canonical-ubuntu-qa team mailing list archive

[Paride Legovini <2067068@xxxxxxxxxxxxxxxxxx>]

@Andreas I've been reminded that arm64 is not an ESM supported
architecture for Xenial, so we should not care about test results for
this specific case. Britney may still flag the test as a failure, but
the SRU team should know to ignore it.

Ideally we should not be attempting a test run, so this bug is in part
still valid, but it is not as bed as I initially thought.

Do we agree on this?

** Description changed:

  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
+   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
+   ubuntu-xenial-16.04-arm64-server-20211001-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.

** Changed in: auto-package-testing
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2067068

Title:
  bos03 has broken arm64 xenial images

Status in Auto Package Testing:
  Incomplete

Bug description:
  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-xenial-16.04-arm64-server-20211001-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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2067068/+subscriptions