Bug #5674
closedUpgrade from 0.66 -> next: upgrade issues because of default caps
0%
Description
Hi,
Due to bugfixes I'm testing, I upgraded all of my OSDs & mons to wip-5655 (c0e77c91b6c39998ef4e19a726db87b66850cf2c), i.e. two commits ahead 921a4aac8a89850303233fe188998202e0ddfe0d (current next).
After trying to restart my radosgw, I got "Couldn't init storage provider (RADOS)" and then radosgw shut down.
After a more careful investigation (--debug-rgw 20 --debug-ms 20), I saw some "Operation not permitted" errors, checked the caps of my key and they were the default (--cap mon 'allow r' --cap osd 'allow rwx').
I guessed that the geo changes would probably involve a new pool and that rgw was trying to create it and failed. I switched its caps to "mon rwx" and it seems to have started properly now.
Unless I'm mistaken, I see three bugs here:
- radosgw should warn about not permitted errors in a non-debug error level,
- the documentation about radosgw caps should be adjusted to "rwx" (or "rw"?)
- dumpling's release notes should be adjust to mention this requirement
Files
Updated by Yehuda Sadeh almost 11 years ago
can you provide a log, so that we can identify what additional log message is missing. From what I can tell, other than that it's really a rados issue.
Updated by Faidon Liambotis almost 11 years ago
- File radosgw.log radosgw.log added
Attached it the log I kept from back before I modified my caps.
Updated by Sage Weil almost 11 years ago
- Priority changed from Urgent to Immediate
Updated by Ian Colle almost 11 years ago
- Status changed from New to Fix Under Review
Updated by Sage Weil almost 11 years ago
- Status changed from Fix Under Review to Resolved
doc fixes are merged. this isn't a new cap requirement. probably you were fine before because the .rgw* pools were already created earlier (that's all the w cap is needed for).