No status information reported when expected-osd-count is not met, causing ceph relations for keys/broker requests to be ignored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceph Monitor Charm |
Fix Released
|
High
|
Trent Lloyd |
Bug Description
If the expected-osd-count is not currently met, the ceph-mon charm intentionally ignores all client-relation-* hooks to provide keys and service broker requests to create pools, etc.
In this specific case, the situation occurred when the cluster was already in production (presumably the count had been met sometime in the past)
This situation is not very obvious, the only log information you see is:
2018-11-29 05:03:47 DEBUG juju-log client:388: insufficient osds bootstrapped
The charm should return this as status information in the juju status output so that it is more clear the ceph cluster is not 'ready' and that is the reason why relations are not being processed. It could possibly also log a non-DEBUG (e.g. INFO) level message each time the relations are skipped though a status check may suffice.
tags: | added: sts |
Changed in charm-ceph-mon: | |
status: | New → Confirmed |
status: | Confirmed → Triaged |
importance: | Undecided → High |
Changed in charm-ceph-mon: | |
milestone: | none → 19.04 |
Changed in charm-ceph-mon: | |
status: | Fix Committed → Fix Released |
Related bug, if you update the config, the relations are not reprocessed: /bugs.launchpad .net/charm- ceph-mon/ +bug/1732491
https:/