# Psmdb-db-rs0 in crashloop after Upgrade

**URL:** <https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460>\
**Category:** Percona Operator for MongoDB\
**Created:** [January 31, 2025, 5:28pm UTC](https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460 "2025-01-31T17:28:22Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![ranjithnairs84](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@ranjithnairs84](https://forums.percona.com/u/ranjithnairs84)\
**Post date:** [January 31, 2025, 5:28pm UTC](https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460/1 "2025-01-31T17:28:22Z")

</div>

psmdb-db-rs0 in crashloop after Percona Mongodb Upgrade (to v6.0.19-16) and Operator Upgrade (to v1.19.0).

---

<div class="post-metadata">

**Author:** ![ranjithnairs84](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@ranjithnairs84](https://forums.percona.com/u/ranjithnairs84)\
**Post date:** [January 31, 2025, 5:30pm UTC](https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460/2 "2025-01-31T17:30:34Z")

</div>

deployed on GKE v 1.30, psmdb-db - statefulSet kind, and psmdb-operator as deployment.

No specific Error messages in pod logs other than :  
exec numactl --interleave=all mongod --bind\_ip\_all --auth --dbpath=/data/db --port=27017 --replSet=rs0 --storageEngine=wiredTiger --relaxPermChecks --clusterAuthMode=x509 --enableEncryption --encryptionKeyFile=/etc/mongodb-encryption/encryption-key --wiredTigerCacheSizeGB=4.16 --wiredTigerIndexPrefixCompression=true --quiet --tlsMode preferTLS --sslPEMKeyFile /tmp/tls.pem --tlsAllowInvalidCertificates --tlsClusterFile /tmp/tls-internal.pem --tlsCAFile /etc/mongodb-ssl/ca.crt --tlsClusterCAFile /etc/mongodb-ssl-internal/ca.crt

---

<div class="post-metadata">

**Author:** ![Julio\_Pasinatto](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/julio_pasinatto/32/17643_2.png) [@Julio\_Pasinatto](https://forums.percona.com/u/Julio_Pasinatto)\
**Post date:** [January 31, 2025, 7:23pm UTC](https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460/3 "2025-01-31T19:23:42Z")

</div>

Hi @ranjithnairs84,

For checking this properly, could you please share the steps you took to upgrade the operator and cluster? Were you using helm charts? What was the previous installed version?

Thanks!

---

<div class="post-metadata">

**Author:** ![Slava\_Sarzhan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/slava_sarzhan/32/3196_2.png) [@Slava\_Sarzhan](https://forums.percona.com/u/Slava_Sarzhan)\
**Post date:** [February 1, 2025, 7:31am UTC](https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460/4 "2025-02-01T07:31:47Z")

</div>

@ranjithnairs84 I can’t reproduce this issue. ☹ did you use our office way [Upgrade MongoDB and the Operator - Percona Operator for MongoDB](https://docs.percona.com/percona-operator-for-mongodb/update.html#upgrade-via-helm) to update your cluster?

---

<div class="post-metadata">

**Author:** ![Srinivasulu\_Kota1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/srinivasulu_kota1/32/19993_2.png) [@Srinivasulu\_Kota1](https://forums.percona.com/u/Srinivasulu_Kota1)\
**Post date:** [February 1, 2025, 11:37am UTC](https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460/5 "2025-02-01T11:37:31Z")

</div>

```
      we are using command to upgrade operator. Operator seem to work fine. helm upgrade "${HELM_RELEASE}" ./helmcharts/psmdb-operator -i -n ${GKE_NAMESPACE} \
      --debug 

```

for database we areusing helm command .  
helm upgrade “${HELM\_RELEASE}” ./helmcharts/psmdb-db -i -n ${GKE\_NAMESPACE}   
–values ./helmcharts/psmdb-db/${LZ\_ENVIRONMENT}-values.yaml --debug  
we are doing in place upgrade.

---

<div class="post-metadata">

**Author:** ![Srinivasulu\_Kota1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/srinivasulu_kota1/32/19993_2.png) [@Srinivasulu\_Kota1](https://forums.percona.com/u/Srinivasulu_Kota1)\
**Post date:** [February 1, 2025, 11:39am UTC](https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460/6 "2025-02-01T11:39:21Z")

</div>

Additional info on versions : Upgrade is done using helm upgrade. Helm-chart values, templates, crds picked up from percona/ percona-helm-charts([GitHub - percona/percona-helm-charts: Collection of Helm charts for Percona Kubernetes Operators.](https://github.com/percona/percona-helm-charts))

helm upgrade percona psmdb-operator from v1.13.0 to v1.19.0  
helm upgrade percona psmdb-db from 5.0.11 to 6.0.19

trying to do in place upgrade.

Other than ERROR without any message , all other messages are informational .

Thanks

---

<div class="post-metadata">

**Author:** ![Slava\_Sarzhan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/slava_sarzhan/32/3196_2.png) [@Slava\_Sarzhan](https://forums.percona.com/u/Slava_Sarzhan)\
**Post date:** [February 3, 2025, 8:49am UTC](https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460/7 "2025-02-03T08:49:46Z")

</div>

@Srinivasulu_Kota1 @ranjithnairs84 In our official doc, the first step is

```auto
kubectl apply --server-side -f https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v1.19.0/deploy/crd.yaml
kubectl apply -f https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v1.19.0/deploy/rbac.yaml

```

In order to update CRDs and RBAC. Helm update can’t update crds.

---

<div class="post-metadata">

**Author:** ![Srinivasulu\_Kota1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/srinivasulu_kota1/32/19993_2.png) [@Srinivasulu\_Kota1](https://forums.percona.com/u/Srinivasulu_Kota1)\
**Post date:** [February 3, 2025, 9:24am UTC](https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460/8 "2025-02-03T09:24:33Z")

</div>

yes. applied crd manually as we noticed that helm did not update crd. check the version update as well.  
rbac is applied using helm .  
mongodb server is not providing any error message but restarting everytime.

---

<div class="post-metadata">

**Author:** ![Slava\_Sarzhan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/slava_sarzhan/32/3196_2.png) [@Slava\_Sarzhan](https://forums.percona.com/u/Slava_Sarzhan)\
**Post date:** [February 3, 2025, 1:00pm UTC](https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460/9 "2025-02-03T13:00:05Z")

</div>

@Srinivasulu_Kota1 Try to check the operator’s log and all logs from different containers (from the affected pod). Also, please check events` kubectl get events --sort-by=.metadata.creationTimestamp`

---

<div class="post-metadata">

**Author:** ![Julio\_Pasinatto](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/julio_pasinatto/32/17643_2.png) [@Julio\_Pasinatto](https://forums.percona.com/u/Julio_Pasinatto)\
**Post date:** [February 3, 2025, 1:35pm UTC](https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460/10 "2025-02-03T13:35:35Z")

</div>

Hi @Srinivasulu_Kota1

I spotted a few issues with your upgrade procedure:

```auto
helm upgrade percona psmdb-operator from v1.13.0 to v1.19.0
helm upgrade percona psmdb-db from 5.0.11 to 6.0.19

```

We only support incremental upgrades of the operator, so going from 1.13.0 to 1.19.0 directly most likely will result in error, please check: [operator upgrade](https://docs.percona.com/percona-operator-for-mongodb/update.html?h=upgra#upgrading-the-operator-and-crd)

Also, we only support `helm upgrade` command for [psmdb-operator](https://docs.percona.com/percona-operator-for-mongodb/update.html?h=upgra#upgrade-via-helm), not psmdb-db, so for the db upgrade, you need to do it manually as described in: [manual upgrade](https://docs.percona.com/percona-operator-for-mongodb/update.html?h=upgra#manual-upgrade_1)

Since you seem to also want to do a major upgrade (going from Mongo 5 → 6) please check [major upgrade](https://docs.percona.com/percona-operator-for-mongodb/update.html?h=upgra#major-version-automated-upgrades) as it can be a more complex operation.

Thanks.

---

<div class="post-metadata">

**Author:** ![Srinivasulu\_Kota](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/srinivasulu_kota/32/9886_2.png) [@Srinivasulu\_Kota](https://forums.percona.com/u/Srinivasulu_Kota)\
**Post date:** [February 3, 2025, 10:23pm UTC](https://forums.percona.com/t/psmdb-db-rs0-in-crashloop-after-upgrade/36460/11 "2025-02-03T22:23:18Z")

</div>

Thank you for the quick response .  
Julio and Salva

given we need to upgrade incrementally , we have decided to do a fresh install and restore the database to version 6.0 .

install happened successfully.