container-image-stream ignored

[Andrew McLeod]

juju 2.4.3

Deployed containers do not appear to honour "container-image-stream" (or image-stream for that matter):

Before (when set to released), from container A:

~$ juju model-config container-image-stream
released

~$ cat /etc/cloud/build.info
build_name: server
serial: 20180823

~$ sudo lxc image list ubuntu-daily:bionic/s390x
+------------+--------------+--------+-------------------------------------------+-------+----------+-------------------------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCH | SIZE | UPLOAD DATE |
+------------+--------------+--------+-------------------------------------------+-------+----------+-------------------------------+
| b (9 more) | f613aca927fc | yes | ubuntu 18.04 LTS s390x (daily) (20180830) | s390x | 165.83MB | Aug 30, 2018 at 12:00am (UTC) |
+------------+--------------+--------+-------------------------------------------+-------+----------+-------------------------------+

After, from container B:

~$ juju model-config container-image-stream
daily

... juju add-unit ...

~$ cat /etc/cloud/build.info
build_name: server
serial: 20180823

[Joseph Phillips (manadart)]

There are a few things that might be at play here.

First, can you verify that there is no value set for "container-image-metadata-url"?

I had a quick scan of the streams on cloud-images.ubuntu.com and there does seem to be both released and daily builds for that architecture. The default is to fall back from released to daily if not found.

Second, note that if Juju has deployed a container, the image will be saved on the machine with a juju-specific alias. This alias does not factor the stream, so if you have an image, change the stream, and deploy a container on the same host, then the alias hit will give the same image as before.

Can you verify whether this is the case?

[Peter Sabaini (peter-sabaini)]

I think I'm seeing this as well.

I indeed do have a juju-specific image alias, and it looks like that (old) image is being used despite model config specifying "daily" images:

peter@pirx ~ » juju model-config | grep image
container-image-metadata-url default ""
container-image-stream model daily
image-metadata-url default ""
image-stream model daily

peter@pirx ~ » juju add-unit ubuntu

peter@pirx ~ » juju ssh 1 -- cat /etc/cloud/build.info
build_name: server
serial: 20201014

peter@pirx ~ » juju machines
...
1 started 10.0.8.232 juju-df9f5a-1 bionic Running

peter@pirx ~ » lxc image list| grep bionic
| juju/bionic/amd64 | b789b81c7261 | no | ubuntu 18.04 LTS amd64 (release) (20201014) | x86_64 | CONTAINER | 188.99MB | Oct 22, 2020 at 10:11am (UTC) |

When deleting the local image I get a fresh copy:

peter@pirx ~ » lxc image delete juju/bionic/amd64

peter@pirx ~ » juju add-unit ubuntu

peter@pirx ~ » juju ssh 2 -- cat /etc/cloud/build.info
build_name: server
serial: 20210125

From `lxc image list ubuntu-daily:` this appears indeed to be the latest image for bionic.

So while deleting images is a workaround to get updated images, as a user I'd still expect to get daily images if the stream is set up for those without manual intervention

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

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.