autopkgtest-buildvm-ubuntu-cloud fails for s390x, armhf, and ppc64el

[Mateus Rodrigues de Morais]

Starting with 5.37ubuntu3, when the change to use ubuntu-minimal images were implemented, we can no longer use the `autopkgtest-buildvm-ubuntu-cloud` script to generate s390x, armhf, and ppc64el images, since there are no ubuntu-minimal images available for these architectures, e.g. [0].

```
ubuntu@autopkgtest-test:~$ autopkgtest-buildvm-ubuntu-cloud -r oracular -a s390x
Downloading https://cloud-images.ubuntu.com/minimal/daily/oracular/current/oracular-minimal-cloudimg-s390x.img...

No image exists for this release/architecture
ubuntu@autopkgtest-test:~$ autopkgtest-buildvm-ubuntu-cloud -r oracular -a armhf
Downloading https://cloud-images.ubuntu.com/minimal/daily/oracular/current/oracular-minimal-cloudimg-armhf.img...

No image exists for this release/architecture
ubuntu@autopkgtest-test:~$ autopkgtest-buildvm-ubuntu-cloud -r oracular -a ppc64el
Downloading https://cloud-images.ubuntu.com/minimal/daily/oracular/current/oracular-minimal-cloudimg-ppc64el.img...

No image exists for this release/architecture
```

As a suggestion to the changes implemented in [1], the if statement should also check which architecture is being used and only switch to minimal if amd64 or arm64.

[0] https://cloud-images.ubuntu.com/minimal/daily/oracular/current/
[1] https://salsa.debian.org/ci-team/autopkgtest/-/commit/4e0e302ab74581da1f33e2d9dbe65b7b1c76c3ba

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Launchpad Janitor (janitor)]

This bug was fixed in the package autopkgtest - 5.42ubuntu2

---------------
autopkgtest (5.42ubuntu2) plucky; urgency=medium

  * tests/testdesc: replace "c64" and "vax" with archs that actually exist

 -- Paride Legovini <email address hidden> Fri, 22 Nov 2024 15:37:37 +0100