Comment 0 for bug 2067068

One first strange thing: apparently for Xenial we don't have an auto-sync/ image, like we have for the other releases, e.g:

  auto-sync/ubuntu-bionic-18.04-arm64-server-20230607-disk1.img
  auto-sync/ubuntu-focal-20.04-arm64-server-20240513-disk1.img

however we have an image with no prefix:

  ubuntu-trusty-14.04-arm64-server-20191107-disk1.img

and build-adt-image appears to be able to find it. However the image fails to boot, and therefore build-adt-image fails to generate an adt/... Xenial image, and we're unable to process xenial arm64 tests on bos03.

A reproducer is on these lines (with the right $secgroup):

openstack server create --flavor autopkgtest --security-group $secgroup --image ubuntu-xenial-16.04-arm64-server-20211001-disk1.img --key-name testbed-juju-7f2275-prod-proposed-migration-environment-3 --network=net_prod-proposed-migration paride-delme-foo

The instance is created, but is not reachable via ssh (this fails: nc -zv <ip> 22). It is not a networking issues as the same with --image auto-sync/ubuntu-bionic-18.04-arm64-server-20230607-disk1.img works.

We should probably get IS to add xenial to the list of images to auto-sync. Hopefully we'll get a working image, and then a working adt/ image will be generated.