Comment 4 for bug 1822331

I agree that someone running disco today and/or after its release could still have the need to create a Ubuntu cloud image based VM for autopkgtest-virt-qemu with precise and trusty.

Especially in the context of our team (Canonical support eng team) + considering the fact that Precise and Trusty are the two first releases not going straight to EOL, but are eligible for ESM (Extended Security Maintenance) provided by UA --> https://www.ubuntu.com/esm

They are going EOL at Ubuntu community point of view, but not at Canonical point of view.

[1] - https://salsa.debian.org/ci-team/autopkgtest.git
$ git show 252c75b7
commit 252c75b767179546382538c5fdd3536783feea2f
Author: Martin Pitt <email address hidden>
Date: Thu Aug 16 16:52:32 2018 +0200

    autopkgtest-buildvm-ubuntu-cloud: Drop obsolete Ubuntu release names

    These are EOL.

diff --git a/tools/autopkgtest-buildvm-ubuntu-cloud b/tools/autopkgtest-buildvm-ubuntu-cloud
index 2ff475c..14eea3f 100755
--- a/tools/autopkgtest-buildvm-ubuntu-cloud
+++ b/tools/autopkgtest-buildvm-ubuntu-cloud
@@ -150,7 +150,7 @@ def parse_args():

 def download_image(cloud_img_url, release, arch):
- if release in ['precise', 'trusty', 'wily', 'xenial']:
+ if release in ['xenial']:
         diskname = '%s-server-cloudimg-%s-disk1.img' % (release, arch)
     else:
         # images were renamed in Ubuntu 16.10