Project

General

Profile

Actions

Bug #5674

closed

Upgrade from 0.66 -> next: upgrade issues because of default caps

Added by Faidon Liambotis almost 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Target version:
-
% Done:

0%

Source:
Community (user)
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

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

radosgw.log (50.8 KB) radosgw.log Faidon Liambotis, 07/19/2013 08:38 AM
Actions

Also available in: Atom PDF