issue afer cross cluster failover and switch from unmanaged to managed cluster

Description

I did the same setup as in blogpost "Disaster Recovery for MongoDB on Kubernetes" with the only difference that after I did failover I also changed "unmanaged: true" to "unmanaged: false" on the second cluster.
The result is that my cluster is stuck in "initializing" state.

Here's how it looks:

Operator logs:

Primary for replicas are elected:

Environment

None

Attachments

1

Activity

Done

Details

Assignee

Reporter

Fix versions

Affects versions

Priority

Created September 13, 2021 at 2:14 PM
Updated March 5, 2024 at 4:47 PM
Resolved September 18, 2021 at 8:39 AM