Travis Nielsen

Please see the [troubleshooting guide](https://rook.github.io/docs/rook/v1.9/Troubleshooting/ceph-common-issues/#monitors-are-the-only-pods-running) for more ideas. In particular, the operator log likely shows an error.

Could you share the full operator log? This snippet doesn't show any errors, just that it is waiting for the mons to be running.

What is the status of the mon pods? Is mon-b in pending state? This is different from the previous state, did you try reinstalling? Perhaps you need to make sure...

The error is: ``` cephosd: skipping osd.1: "8a90dfa5-02af-459e-a588-64b31fbabd8a" belonging to a different ceph cluster "31e24704-114f-4947-b2f1-ed98ca02fddc" ``` Where osd.1 had already been created on vdb in a different cluster. So it...

Yes you need a fresh disk. The same disk cannot be used between different clusters.

@leiw324 You have the default cluster.yaml with `useAllNodes: true` and `useAllDevices: true`? Then if you have three nodes, you should see three osd-prepare pods. Are any of the nodes tainted?

> since it is failing in the CI because of there deprecated v1beta1 cronjob I see v0.5.4 is the latest whereabouts release, perhaps that has a fix?

> > > since it is failing in the CI because of there deprecated v1beta1 cronjob > > > > > > I see v0.5.4 is the latest whereabouts release,...

@subhamkrai Ready for merge, right? It still has the do-not-merge label

@smasset-orange In your testing do we need different RBAC for the v1.7 backport? If so we can close this one and you can open a new one.