client relations are never processed when configuration change (monitor-count, expected-osd-count) causes cluster to become ready
Bug #1732491 reported by
Edward Hope-Morley
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceph Monitor Charm |
Fix Released
|
Medium
|
Trent Lloyd |
Bug Description
If i deploy 1 unit of ceph-mon with monitor-count=3 it failes to bootstrap as expected. If i then set monitor-count=1 i would expect it to then bootstap but instead it does nothing and I have to remove and re-add the ceph client relations to get it to happen.
Changed in charm-ceph-mon: | |
status: | New → Triaged |
Changed in charm-ceph-mon: | |
milestone: | 17.11 → 18.02 |
Changed in charm-ceph-mon: | |
milestone: | 18.02 → 18.05 |
Changed in charm-ceph-mon: | |
milestone: | 18.05 → 18.08 |
Changed in charm-ceph-mon: | |
milestone: | 18.08 → 18.11 |
Changed in charm-ceph-mon: | |
milestone: | 18.11 → 19.04 |
summary: |
- failed bootstrap due to incorrect monitor-count is unresolvable + client relations are never processed when configuration change (monitor- + count, expected-osd-count) causes cluster to become ready |
Changed in charm-ceph-mon: | |
milestone: | 19.04 → 19.07 |
Changed in charm-ceph-mon: | |
milestone: | 19.07 → 19.10 |
Changed in charm-ceph-mon: | |
milestone: | 19.10 → 20.01 |
To post a comment you must log in.
I have now found some additional issues with this logic. If I start by deploying 3 units with monitor-count=1 (which I know if wrong) what happens is that all 3 units will bootstrap independently i.e. at the point at which they have what they consider to be sufficient hosts i.e. 1 a.k.a themselves. The problem is that if I then set monitor-count=3 it remains wedged and the only way to fix it is to delete 2 units and start again. The same is also True if I have N mon units with monitor-count=N and i scale out my ceph-mon application before updating monitor-count. I think the charm should be able to manage these scenarios somehow.