# When Changing to allowUnsafeConfigurations: true cluster goes to failuresand ongos doesnot get to Ready state **URL:** \ **Category:** Percona Operator for MongoDB\ **Tags:** percona, bugs\ **Created:** [September 19, 2022, 10:36am UTC](https://forums.percona.com/t/when-changing-to-allowunsafeconfigurations-true-cluster-goes-to-failuresand-ongos-doesnot-get-to-ready-state/17547 "2022-09-19T10:36:30Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Yossi\_Cohn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yossi_cohn/32/5731_2.png) [@Yossi\_Cohn](https://forums.percona.com/u/Yossi_Cohn)\ **Post date:** [September 19, 2022, 10:36am UTC](https://forums.percona.com/t/when-changing-to-allowunsafeconfigurations-true-cluster-goes-to-failuresand-ongos-doesnot-get-to-ready-state/17547/1 "2022-09-19T10:36:30Z")
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 ---
**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\ **Post date:** [October 19, 2022, 7:26pm UTC](https://forums.percona.com/t/when-changing-to-allowunsafeconfigurations-true-cluster-goes-to-failuresand-ongos-doesnot-get-to-ready-state/17547/2 "2022-10-19T19:26:01Z")
Hello @Yossi_Cohn , sorry for not responding sooner - the topic is created in a non-operator thread and was ignored. Yeah, I was able to reproduce it unfortunately. Also I see you created the ticket for it here [[K8SPSMDB-786] When Changing to allowUnsafeConfigurations: true cluster goes to failuresand ongos doesnot get to Ready state - Percona JIRA](https://jira.percona.com/browse/K8SPSMDB-786) The dirty fix here would be to delete this mongos pod. It will then get into running state automatically. We will check with the team what might be the issue and update the JIRA ticket.