Actions
Bug #46139
closedprofile rbd does not allow the use of RBD_INFO
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
nautilus,octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
pretty much like https://tracker.ceph.com/issues/39973 but this time a client restricted to a namespace cannot create images,
The failure is :
2020-06-22T12:16:17.871+0200 7fd6e14f5700 -1 librbd::image::ValidatePoolRequest: handle_read_rbd_info: failed to read RBD info: (1) Operation not permitted 2020-06-22T12:16:17.871+0200 7fd6e14f5700 -1 librbd::image::CreateRequest: 0x55a8e72a5190 handle_validate_data_pool: failed to validate pool: (1) Operation not permitted rbd: create error: (1) Operation not permitted
This can be resolved by adding the following cap to the client :
allow r pool rbd object_prefix rbd_info
I have successfully resolved the bug on my end by adding the necessary bits to src/osd/OSDCap.cc
I will open a PR on github.com shortly
I have not filled in the Backport filled, but looks like it happens on all the rbd-namespace-enabled releases.
Updated by Florian Florensa almost 4 years ago
Updated by Jason Dillaman almost 4 years ago
- Project changed from Ceph to rbd
- Backport set to nautilus,octopus
Updated by Jason Dillaman almost 4 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 35699
Updated by Jason Dillaman almost 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46321: nautilus: profile rbd does not allow the use of RBD_INFO added
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46322: octopus: profile rbd does not allow the use of RBD_INFO added
Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions