Requested image's type 'virtual-machine' doesn't match instance type 'container'

[Felipe Reyes]

When deploying a bundle using the maas provider the lxd containers fail at deployment time, this is happening with juju 2.9.14-37b938f (2.9/edge channel), as can been seen in juju status the containers created in machine 2 started successfully, only for machines 1 and 3 failed.

There is a lxd issue filed last year https://github.com/lxc/lxd/issues/8117 where they say this is not a lxd issue instead how juju is using lxd.

$ juju status
[...]
Machine State DNS Inst id Series AZ Message
0 started 10.0.0.169 node1 focal default Deployed
1 started 10.0.0.170 node4 focal default Deployed
1/lxd/0 down pending focal Requested image's type 'virtual-machine' doesn't match instance type 'container'
1/lxd/1 down pending focal Requested image's type 'virtual-machine' doesn't match instance type 'container'
1/lxd/2 down pending focal Requested image's type 'virtual-machine' doesn't match instance type 'container'
1/lxd/3 down pending focal Requested image's type 'virtual-machine' doesn't match instance type 'container'
1/lxd/4 down pending focal Requested image's type 'virtual-machine' doesn't match instance type 'container'
1/lxd/5 down pending focal Requested image's type 'virtual-machine' doesn't match instance type 'container'
2 started 10.0.0.171 node3 focal default Deployed
2/lxd/0 started 10.0.0.175 juju-cf3fde-2-lxd-0 focal default Container started
2/lxd/1 started 10.0.0.177 juju-cf3fde-2-lxd-1 focal default Container started
2/lxd/2 started 10.0.0.176 juju-cf3fde-2-lxd-2 bionic default Container started
2/lxd/3 started 10.0.0.174 juju-cf3fde-2-lxd-3 focal default Container started
2/lxd/4 started 10.0.0.173 juju-cf3fde-2-lxd-4 focal default Container started
3 started 10.0.0.172 node2 focal default Deployed
3/lxd/0 down pending focal Requested image's type 'virtual-machine' doesn't match instance type 'container'
3/lxd/1 down pending focal Requested image's type 'virtual-machine' doesn't match instance type 'container'
3/lxd/2 down pending focal Requested image's type 'virtual-machine' doesn't match instance type 'container'
3/lxd/3 down pending focal Requested image's type 'virtual-machine' doesn't match instance type 'container'
3/lxd/4 down pending focal Requested image's type 'virtual-machine' doesn't match instance type 'container'

$ snap info juju | grep installed
installed: 2.9.14-37b938f (17186) 106MB classic

Bundle: https://paste.ubuntu.com/p/28TjKBcQqq/
juju show-controller: https://paste.ubuntu.com/p/9GfkGY3tff/

crashdump: https://private-fileshare.canonical.com/~freyes/juju-crashdump-7c63dbb4-ad89-46d6-883b-92dc4d0ba59b.tar.xz
crashdump controller model: https://private-fileshare.canonical.com/~freyes/juju-crashdump-7c63dbb4-ad89-46d6-883b-92dc4d0ba59b.tar.xz

[John A Meinel (jameinel)]

It seems that LXD has started publishing multiple images with the same key that we use to look up the mapping from a series to an image. They added an additional field to distinguish them, but it wasn't a field that existed in the past that we had support for filtering. And it would seem that as we are iterating to pick an image, there is the chance that any given machine could map the image in a different fashion.

[Joseph Phillips (manadart)]

https://github.com/juju/juju/pull/13359