Parth Arora
@alyti can you mention the operator logs, where you see it's unparsable, And also what you provided in the yaml's(cluster.yaml,etc)
> Both versions are the same, only the commit id is different. What commit-id is difference? > Install canonical ceph on proxmox. rook-ceph-operator no longer throws an error. Does this...
Yaa so the problem is with `DeepEqual` , So what do you want us to fix, I see in the latest ceph versions we install ceph using `cephadm` only
>I'd like to suggest comparing the version parts (major, minor,... without CommitID) instead of DeepEqual. Installing with cephadm from Proxmox is not a normal way. I have a dependency problem....
Second commit >[core: only generate operator keyring after mon quorum](https://github.com/rook/rook/pull/10190/commits/fdc645277bf1d3e605278de23e9a5df8b284dc32) The operator keyring should only be generated by the main reconcile after the mons have formed quorum and to ensure...
We sync it here mon-ip with endpoint details here, https://github.com/rook/rook/blob/5a82a1cbd737a9062df883cb48c2785c253fa1f5/pkg/operator/ceph/cluster/mon/mon.go#L558
Can please you share the operator logs?
Yaa I can understand the problem, it's a race condition which occurred, Thanks for explaining this I will discuss with the team about this issue,
> if operator restart before removeMon(), the new mon endpoint record left over in cm , As an operator, it should reconcile to keep up the desired state, So even...