# Mongodb HELM chart upgrade from 1.10 to 1.11 fails

**URL:** <https://forums.percona.com/t/mongodb-helm-chart-upgrade-from-1-10-to-1-11-fails/16777>\
**Category:** MongoDB\
**Tags:** mongodb\
**Created:** [July 27, 2022, 10:22am UTC](https://forums.percona.com/t/mongodb-helm-chart-upgrade-from-1-10-to-1-11-fails/16777 "2022-07-27T10:22:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![a.starman](https://avatars.discourse-cdn.com/v4/letter/a/848f3c/32.png) [@a.starman](https://forums.percona.com/u/a.starman)\
**Post date:** [July 27, 2022, 10:22am UTC](https://forums.percona.com/t/mongodb-helm-chart-upgrade-from-1-10-to-1-11-fails/16777/1 "2022-07-27T10:22:08Z")

</div>

Hi all!  
I am new in Percona and Mongodb and have problems with HELM upgrade of Percona packages.  
First i installed Percona HELM charts:  
psmdb-operator-1.10.0.tgz  
psmdb-db-1.10.0.tgz

Then i upgrade to 1.11 using HELM upgrade commands. Operator psmdb-operator-1.11.0.tgz upgrades OK, but when upgrading to psmdb-db-1.11.0.tgz i get an error:  
Error: UPGRADE FAILED: rendered manifests contain a resource that already exists. Unable to continue with update: Secret “mongodb-10-psmdb-db-secrets” in namespace “mongodb” exists and cannot be imporinvalid ownership metadata; label validation error: missing key “[app.kubernetes.io/managed-by](http://app.kubernetes.io/managed-by)”: must be set to “Helm”; annotation validation error: missing key “meta.helm.sh/release-name”: must be setalidation error: missing key “meta.helm.sh/release-namespace”: must be set to “mongodb”

What is the problem here?

Best regards, Anton

---

<div class="post-metadata">

**Author:** ![marcun](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@marcun](https://forums.percona.com/u/marcun)\
**Post date:** [August 5, 2022, 12:44pm UTC](https://forums.percona.com/t/mongodb-helm-chart-upgrade-from-1-10-to-1-11-fails/16777/2 "2022-08-05T12:44:59Z")

</div>

Hello.

I have been doing similar testing and got the same issue.

The problem seems to be with psmdb-db/templates/cluster-secret.yaml. The first line of code was changed from `{{- if not .Values.users }}` in version 1.10.0 to `{{- if not (hasKey .Values.secrets "users") }}` in version 1.11.0.

When deploying version 1.10.0, it seems that cluster-secret.yaml is not run, because the users in values.yaml are defined. However, for some reason, secret “my-db-psmdb-db-secrets” is still deployed (I assume by the operator). If I describe the generated secret the output is:

```auto
Name: my-db-psmdb-db-secrets
Namespace: mongodb
Labels: <none>
Annotations: <none>

Type: Opaque

Data
====
MONGODB_USER_ADMIN_USER: 9 bytes
MONGODB_BACKUP_PASSWORD: 19 bytes
MONGODB_BACKUP_USER: 6 bytes
MONGODB_CLUSTER_ADMIN_PASSWORD: 17 bytes
MONGODB_CLUSTER_ADMIN_USER: 12 bytes
MONGODB_CLUSTER_MONITOR_PASSWORD: 16 bytes
MONGODB_CLUSTER_MONITOR_USER: 14 bytes
MONGODB_USER_ADMIN_PASSWORD: 16 bytes

```

When upgrading to 1.11.0 (with helm upgrade) cluster-secret.yaml is run (because of that if statement in the first line of code). cluster-secret.yaml then also tries to generate some additional labels and annonations in the secret, which then causes a conflict and we get the error described above. If install version 1.11.0 (without any upgrades) and describe the deployed secreted the output is (note the labels and annonations):

```auto
Name: my-db-psmdb-db-secrets
Namespace: mongodb
Labels: app.kubernetes.io/instance=my-db
              app.kubernetes.io/managed-by=Helm
              app.kubernetes.io/name=psmdb-db
              app.kubernetes.io/version=1.11.0
              helm.sh/chart=psmdb-db-1.11.0
Annotations: meta.helm.sh/release-name: my-db
              meta.helm.sh/release-namespace: mongodb

Type: Opaque

Data
====
MONGODB_BACKUP_USER: 6 bytes
MONGODB_CLUSTER_ADMIN_USER: 12 bytes
MONGODB_CLUSTER_MONITOR_PASSWORD: 20 bytes
MONGODB_USER_ADMIN_USER: 9 bytes
MONGODB_BACKUP_PASSWORD: 12 bytes
MONGODB_CLUSTER_ADMIN_PASSWORD: 18 bytes
MONGODB_CLUSTER_MONITOR_USER: 14 bytes
MONGODB_USER_ADMIN_PASSWORD: 15 bytes
PMM_SERVER_PASSWORD: 5 bytes
PMM_SERVER_USER: 5 bytes

```

The solution to successfully upgrade from 1.10.0 to 1.11.0 seems to be to manually patch “my-db-psmdb-db-secrets” secret and add the missing labels and annonations before upgrading.

Since I am also new to mongodb and kubernetes, I am wondering if for example there is a similar problem when running helm upgrade in production, should the kubernetes resources be fixed manually, or how is this usually done?

Best regards