Every time I update a deployments image tag, have to remove persistent folder, update, then add it back

[nodesocket]

Ask a Question!

Every time I update a deployments image tag, I have to manually remove the persistent folder (pvc), click update, and then edit the deployment again and add back the persistent folder with the same existing pvc settings. Shouldn't I be able to just update the image tag without this process? If I don't remove the persistent folder beforehand I get the error:

persistentvolumeclaims "myapp-e2552340-2f99-4925-b4f6-e9071611c731" already exists

[Nick-Portainer]

Hello @nodesocket Can you please provide more information around your deployment of Portainer server and how you are deploying your applications, so I can attempt to replicate this.

[nodesocket]

@Nick-Portainer I'll ty to provide as much detail as possible, let me know if you need any other info.

Portainer Version: 2.21.5
Kubernetes Version: v1.28.15
Arch: arm64

Created a brand new helloworld Deployment application using form method. image: buoyantio/helloworld:0.1.7. 1GB new persistent folder mounted to /data.

After helloworld Deployment application deployed, I clicked edit application and attempted to change the tag to latest. And see the following error:

Note: changing any aspect of the application, not just the image tag, e.g. cpu limit results in this error. I have to manually delete the persistent folder, click update, then go back and re-attach the persistent folder to the Deployment.

[nodesocket]

@Nick-Portainer any update? Were you able to replicate?

[Nick-Portainer]

@nodesocket I have created an internal ticket for the team to look into this, appears to be a potential bug.

internal: BE-11565

[nodesocket]

@Nick-Portainer thanks for the follow up. I'm a bit surprised I am the only one who reported this as it seems like a very common bug that would affect others. Is there another issue related to my discussion here?