### Author:  [@oldev](https://hub.mender.io/u/oldev)
#### Post date: [September 8, 2023, 11:15am UTC](https://hub.mender.io/t/deployment-of-aks-based-mender-server-version-3-6-2-not-completely-successful/6190/25 "2023-09-08T11:15:11Z")
I will re-install. I dug into the chart and have seen quite some logic around the mongo uri generation.
I had a request to scale down pods in the cluster and did in fact change the mongodb architecture at one helm revision.
>
---
### Author:  [@oldev](https://hub.mender.io/u/oldev)
#### Post date: [September 8, 2023, 11:21am UTC](https://hub.mender.io/t/deployment-of-aks-based-mender-server-version-3-6-2-not-completely-successful/6190/26 "2023-09-08T11:21:39Z")
Should I keep these properties in my config for fresh installation regarding the NATS issue?
```auto
workflows:
automigrate: false
create_artifact_worker:
automigrate: false
```
---
### Author:  [@robgio](https://hub.mender.io/u/robgio)
#### Post date: [September 8, 2023, 11:33am UTC](https://hub.mender.io/t/deployment-of-aks-based-mender-server-version-3-6-2-not-completely-successful/6190/27 "2023-09-08T11:33:19Z")
Yes, you can keep the `automigrate: false` flags.
The `mongodb-common-prerelease` could be originating from the old setup, then. When doing a fresh install you also have to take care of old volumes, that usually are kept even after a helm delete.
Tldr: for a real fresh install you have to delete all the secrets, pvc, pv, jobs, statefulset resources that could be kept even after an `helm delete`
---
### Author:  [@oldev](https://hub.mender.io/u/oldev)
#### Post date: [September 8, 2023, 12:02pm UTC](https://hub.mender.io/t/deployment-of-aks-based-mender-server-version-3-6-2-not-completely-successful/6190/28 "2023-09-08T12:02:49Z")
The cluster is cleaned and ready.
Now I get an yaml error when I set
workflows.automigrate=false
```bash
\o$ helm template mender mender/mender -f mender-3.6.2.yml --set workflows.automigrate=true > /dev/null
\o$ helm template mender mender/mender -f mender-3.6.2.yml --set workflows.automigrate=false > /dev/null
Error: YAML parse error on mender/templates/create-artifact-worker-deploy.yaml: error converting YAML to JSON: yaml: line 55: mapping values are not allowed in this context
Use --debug flag to render out invalid YAML
```
---
### Author:  [@robgio](https://hub.mender.io/u/robgio)
#### Post date: [September 8, 2023, 12:28pm UTC](https://hub.mender.io/t/deployment-of-aks-based-mender-server-version-3-6-2-not-completely-successful/6190/29 "2023-09-08T12:28:21Z")
Checking… Can you please try without the `automigrate` flags meanwhile?
---
### Author:  [@oldev](https://hub.mender.io/u/oldev)
#### Post date: [September 8, 2023, 12:33pm UTC](https://hub.mender.io/t/deployment-of-aks-based-mender-server-version-3-6-2-not-completely-successful/6190/30 "2023-09-08T12:33:56Z")
I did run 2 template of the specific file:
```auto
helm template mender ./mender -f mender-3.6.2-2.yml -s templates/create-artifact-worker-deploy.yaml --debug --version 5.2.3 --set workflows.automigrate=true > good_create-artifact-worker-deploy.yaml
helm template mender ./mender -f mender-3.6.2-2.yml -s templates/create-artifact-worker-deploy.yaml --debug --version 5.2.3 --set workflows.automigrate=false > cursed_create-artifact-worker-deploy.yaml
diff cursed_create-artifact-worker-deploy.yaml good_create-artifact-worker-deploy.yaml
57c57,58
< memory: 128Mcommand: ["workflows", "--config", "/etc/workflows/config.yaml", "worker"]
---
> memory: 128M
> command: ["workflows", "--config", "/etc/workflows/config.yaml", "worker", "--automigrate"]
```
There’s no linebreak after memory: 128M 😵💫
---
### Author:  [@oldev](https://hub.mender.io/u/oldev)
#### Post date: [September 8, 2023, 12:58pm UTC](https://hub.mender.io/t/deployment-of-aks-based-mender-server-version-3-6-2-not-completely-successful/6190/31 "2023-09-08T12:58:23Z")
The clean setup even without `automigrate` flags was successful. I can’t tell what the difference was to the previous installation. Maybe some special character as I’m not working 100% with linux ☹
Thanks for the quick and excellent support!
```auto
kubectl get pods
NAME READY STATUS RESTARTS AGE
mender-api-gateway-7b75c59bdd-bpsf8 1/1 Running 0 8m44s
mender-create-artifact-worker-6b9f44d949-wd4wz 1/1 Running 3 (8m3s ago) 8m44s
mender-deployments-6f6764995c-pk28g 1/1 Running 0 8m44s
mender-device-auth-989c8bd96-jdzvk 1/1 Running 0 8m44s
mender-deviceconfig-67b9779b8d-qhhl8 1/1 Running 0 8m44s
mender-deviceconnect-5b67d847f-58qtx 1/1 Running 0 8m44s
mender-gui-5d999776c4-sr22k 1/1 Running 0 8m44s
mender-inventory-8899485fb-4c85p 1/1 Running 0 8m44s
mender-iot-manager-587ff944d-sshmr 1/1 Running 0 8m44s
mender-mongodb-0 1/1 Running 0 9m42s
mender-mongodb-1 1/1 Running 0 9m
mender-mongodb-arbiter-0 1/1 Running 0 9m41s
mender-nats-0 3/3 Running 0 8m44s
mender-nats-1 3/3 Running 0 8m44s
mender-nats-2 3/3 Running 0 8m44s
mender-nats-box-7bbc67486c-hzrcm 1/1 Running 0 8m44s
mender-redis-master-0 1/1 Running 0 9m39s
mender-redis-replicas-0 1/1 Running 0 9m38s
mender-redis-replicas-1 1/1 Running 0 8m52s
mender-redis-replicas-2 1/1 Running 0 8m27s
mender-useradm-7d9d56b6fd-nmn5z 1/1 Running 0 8m44s
mender-workflows-server-5cc4b8b965-j78lz 1/1 Running 2 (8m21s ago) 8m44s
mender-workflows-worker-859b66449-zgzbt 1/1 Running 3 (8m7s ago) 8m44s
```
---
### Author:  [@robgio](https://hub.mender.io/u/robgio)
#### Post date: [September 8, 2023, 1:01pm UTC](https://hub.mender.io/t/deployment-of-aks-based-mender-server-version-3-6-2-not-completely-successful/6190/32 "2023-09-08T13:01:10Z")
Thanks for the debug! FYI, here’s a PR for the fix you reported: [fix: automigrate command newline fix by oldgiova · Pull Request #196 · mendersoftware/mender-helm · GitHub](https://github.com/mendersoftware/mender-helm/pull/196)
Have a great weekend.
[Previous page](https://hub.mender.io/t/deployment-of-aks-based-mender-server-version-3-6-2-not-completely-successful/6190.md?page=1)