Cisco Bug: CSCvu84169 - JIRA Bug: MAGLEV-11940 -- Oplog Tailer initialize failed, Re-join of Old active stuck in Configure s
Jul 21, 2020
- Cisco DNA Center
Known Affected Releases
Symptom: After a DR failover, the subsequent DR rejoin failed with dr-mongodb-replicator stuck in CrashLoopBackOff state, with logging error: "Oplog Tailer initialize failed: ... node is recovering" Conditions: This happens when one or both of the MongoDB standby nodes are in "RECOVERING" state on the DR active cluster side. Since the new DR active cluster was the original DR passive cluster before the DR failover, the MongoDB standby nodes stuck in "RECOVERING" state may have occurred before the DR failover operation.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases