container-image-metadata-url changes not affected after model deployment

[Narinder Gupta]

It seems changes in container-image-metadata-url after the model deployment are not considered. There should be a way to update this url on deployed model as well.
Use case: If using any repo for containers but want to use standard repo for future this should be considered.

In my case i have setup container-image-metadata-url: https://lxdkvm-images.prod.maas/ now i want to use container-image-metadata-url: https://cloud-images.ubuntu.com/ as standard metadata.

[Joseph Phillips (manadart)]

Can you provide the Juju version that you are using, the command you used to set the config value initially, and the command you used to change it?

[Narinder Gupta (narindergupta)]

I am using juju version 2.4.5 and i am defining
container-image-metadata-url to private repository. After deployment of model i wanted to switch to different repository and wanted to update this metadata repo on deployed nodes as well. I can confirm online the nodes where lxd container was not created only uses the new repo. But if lxd container is already deployed and if i create new container it still refers to old repository.

[Anastasia (anastasia-macmood)]

Removing from a milestone as this work will not be done in 2.5 series.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.