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

Bug #1797168 reported by Narinder Gupta on 2018-10-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

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: now i want to use container-image-metadata-url: as standard metadata.

Joseph Phillips (manadart) wrote :

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?

Changed in juju:
status: New → Incomplete
assignee: nobody → Joseph Phillips (manadart)
Narinder Gupta (narindergupta) wrote :

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.

Changed in juju:
status: Incomplete → New
tags: added: cpe-onsite
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.5.1
Ian Booth (wallyworld) on 2019-01-28
Changed in juju:
milestone: 2.5.1 → 2.5.2
Changed in juju:
assignee: Joseph Phillips (manadart) → nobody
Changed in juju:
milestone: 2.5.2 → 2.5.3
Changed in juju:
milestone: 2.5.3 → 2.5.4
Changed in juju:
milestone: 2.5.4 → 2.5.5
Changed in juju:
milestone: 2.5.6 → 2.5.8
Changed in juju:
milestone: 2.5.8 → 2.5.9
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers