Bug #15776
rgw: more descriptive error message when failing to read zone/realm/zg info
% Done:
0%
Source:
other
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Currently if rgw is started with an improper zonegroup/zone/realm option, the log only says the following:
2016-05-09 10:22:16.339583 7f2885a82ac0 0 error in read_id for id : (2) No such file or directory
We could do better here by logging the object name instead
Related issues
History
#2 Updated by Abhishek Lekshmanan almost 8 years ago
- Status changed from New to Fix Under Review
#3 Updated by Abhishek Lekshmanan almost 8 years ago
- Status changed from Fix Under Review to Resolved
#4 Updated by Wido den Hollander over 7 years ago
This is marked as resolved, but on 10.2.5 I am still seeing it:
root@alpha:~# radosgw-admin period update --commit 2016-12-22 13:05:56.736025 7fd05c000a00 0 error in read_id for id : (2) No such file or directory 2016-12-22 13:05:56.737007 7fd05c000a00 0 error in read_id for id : (2) No such file or directory 2016-12-22 13:06:00.950629 7fd05c000a00 1 error read_lastest_epoch .rgw.root:periods.422e4a8f-76b6-4692-9c83-f31fdc46b4a5.latest_epoch { "id": "422e4a8f-76b6-4692-9c83-f31fdc46b4a5", "epoch": 1, ... ... } root@alpha:~# ceph -v ceph version 10.2.5 (c461ee19ecbc0c5c330aca20f7392c9a00730367) root@alpha:~#
Pull request #8994 was merged into master, but was never backported to Jewel.
So these messages are still printed in the current Jewel release.
Backport PR: https://github.com/ceph/ceph/pull/12622
#5 Updated by Nathan Cutler over 7 years ago
- Status changed from Resolved to Pending Backport
- Backport set to jewel
#6 Updated by Nathan Cutler over 7 years ago
- Copied to Backport #18340: jewel: rgw: more descriptive error message when failing to read zone/realm/zg info added
#7 Updated by Nathan Cutler about 7 years ago
- Status changed from Pending Backport to Resolved