# Psmdb operator fails to complete smart update **URL:** \ **Category:** Percona Operator for MongoDB\ **Created:** [October 4, 2023, 3:07pm UTC](https://forums.percona.com/t/psmdb-operator-fails-to-complete-smart-update/25660 "2023-10-04T15:07:25Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Slavisa\_Milojkovic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/slavisa_milojkovic/32/7097_2.png) [@Slavisa\_Milojkovic](https://forums.percona.com/u/Slavisa_Milojkovic)\ **Post date:** [October 4, 2023, 3:20pm UTC](https://forums.percona.com/t/psmdb-operator-fails-to-complete-smart-update/25660/2 "2023-10-04T15:20:28Z")
This is the same issue caused by operator smart update failure > [@ReplicaSet host unreachable](https://forums.percona.com/t/replicaset-host-unreachable/21286/11): > > Hello, I still have this issue. I narrowed it down and it seems that the operator can’t recover the cluster once it starts the smart update. Can this update be disabled and how it detects that statefulset is not up to date? So when this happens, 2 psmdb-cfg pods are restarted and the third one is not (age is different), also all of the 3 mongos pods are displaying readiness error When I delete the third cfg pod, operator continues to restart rs0 pods one by one and mongos one by one.… --- _[View the full topic](https://forums.percona.com/t/psmdb-operator-fails-to-complete-smart-update/25660)._