Charm stays in blocked state due unresolved permission issue when connected to a Ceph Octopus cluster
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceph RBD Mirror Charm |
Triaged
|
High
|
Unassigned |
Bug Description
Even though we request keys from ceph with an rbd-mirror profile the rbd-mirror process appears to not be able to interact with the Ceph cluster in the way it expects at Octopus. We also made an attempt to give the rbd-mirror user full access to the mon.
Enabling debug log on the MON may give log output such as:
2020-05-
2020-05-
2020-05-
The first side effect of this is that Ceph will mark any mirrored image/pool as being in a WARNING state, despite the fact that data appears to be mirrored, subsequently the charm will report this and be stuck in a blocked state.
At this stage in discovery our opinion is that this must be an upstream Ceph Octopus bug, but we keep this as a charm bug for tracking until we have final confirmation.
Changed in charm-ceph-rbd-mirror: | |
status: | New → Triaged |
importance: | Undecided → High |
description: | updated |
description: | updated |
This may be an upstream bug so I have raised https:/ /tracker. ceph.com/ issues/ 45638