Rook only requires a single mon to seed the external cluster, but then it is expected that Rook will query for the full mon quorum periodically and update the configmap with the full set of mons. @Rachael Was the mon down since OCS first connected, or did the mon go down after that initial connection? The rook operator log [1] is full of these messages. Since it says it could connect successfully, it doesn't make sense why it stilled the health check. 2020-08-03T08:35:13.798015964Z 2020-08-03 08:35:13.797974 W | op-mon: skipping mon health check since cluster details are not initialized 2020-08-03T08:35:24.325634174Z 2020-08-03 08:35:24.325596 I | op-config: CephCluster "openshift-storage" status: "Connected". "Cluster connected successfully" [1] http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/BZ-1867130/must-gather.local.9029136130735763706/quay-io-rhceph-dev-ocs-must-gather-sha256-6639c93bf3de91c2a71d069d2e2516d6b4aa894b8101852abb8a0aafccfa976c/ceph/namespaces/openshift-storage/pods/rook-ceph-operator-66c694f9b9-c5jjw/rook-ceph-operator/rook-ceph-operator/logs/current.log
Neha, the cm "regression" is due to the bug and will be solved by my current PR. Expect this to land today. Thanks
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenShift Container Storage 4.5.0 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:3754