Comment 2 for bug 1790151

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