When Changing to allowUnsafeConfigurations: true cluster goes to failures and mongos does not get to Ready state

Description

Using the Helm Chart for PSMDB
Chart Version: 1.12.4
Operator Version: 1.12.0
When changing to (was false) allowUnsafeConfigurations: true
The cluster starts to reinitialize the replicasets pods and eventually the mongos cannot get to Ready State.
Moreover, it seems that the replicaset could not get one of the nodes as Primary.

To simulate:
Just run any CR with allowUnsafeConfigurations: false and then change to allowUnsafeConfigurations: true.

btw, I think pertains to another issue with pause: true which also means changing to allowUnsafeConfigurations: true and then the cluster fails when coming back with pause: false

2 birds in one bug

Environment

None

Smart Checklist

Activity

Show:

ege.gunes April 24, 2024 at 12:44 PM

Fixed under another ticket.

Tomislav Plavcic April 24, 2024 at 12:24 PM

Done

Details

Assignee

Reporter

Needs QA

Fix versions

Priority

Smart Checklist

Created September 19, 2022 at 10:50 AM
Updated April 24, 2024 at 12:44 PM
Resolved April 24, 2024 at 12:43 PM

Flag notifications