No status information reported when expected-osd-count is not met, causing ceph relations for keys/broker requests to be ignored

[Trent Lloyd]

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.

[Trent Lloyd (lathiat)]

Related bug, if you update the config, the relations are not reprocessed:
https://bugs.launchpad.net/charm-ceph-mon/+bug/1732491

[Trent Lloyd (lathiat)]

Fix Proposed: https://review.openstack.org/#/c/624013/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/624013
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=1a250e81a5570bfbd7bae64f63a5d713e9238b20
Submitter: Zuul
Branch: master

commit 1a250e81a5570bfbd7bae64f63a5d713e9238b20
Author: Trent Lloyd <email address hidden>
Date: Mon Dec 10 15:58:23 2018 +0800

    Set waiting status when number of OSDs has not yet reached expected-osd-count

    The charm does not process relation requests from clients when the
    number of OSDs has not yet reached the expected-osd-count.

    Make this situation clear to the user by setting the charm status to
    waiting with relevant information.

    Change-Id: I638547ca4a9f1bf48782c82aa0d92f89f6bfd13a
    Closes-Bug: 1807652