[Bug 1822331] Re: autopkgtest-buildvm-ubuntu-cloud no longer works with precise or trusty

[Eric Desrochers]

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 <martin at piware.de>
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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1822331

Title:
  autopkgtest-buildvm-ubuntu-cloud no longer works with precise or
  trusty

Status in autopkgtest package in Ubuntu:
  In Progress
Status in autopkgtest source package in Disco:
  In Progress
Status in autopkgtest package in Debian:
  New

Bug description:
  [impact]

  creation of qemu imgs for use with autopkgtest-virt-qemu is done with
  the autopkgtest-buildvm-ubuntu-cloud program.  This was dropped in
  version 5.6:

        [ Martin Pitt ]
        * autopkgtest-buildvm-ubuntu-cloud: Drop obsolete Ubuntu release names

  diff --git a/tools/autopkgtest-buildvm-ubuntu-cloud b/tools/autopkgtest-buildvm-ubuntu-cloud
  index 2ff475c..81b4304 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

  however, precise and trusty are not 'obsolete Ubuntu release names'
  just yet.

  [test case]

  run autopkgtest-buildvm-ubuntu-cloud with either -r precise or -r
  trusty:

  $ autopkgtest-buildvm-ubuntu-cloud -r trusty
  Downloading https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64.img...

  No image exists for this release/architecture
  $ autopkgtest-buildvm-ubuntu-cloud -r precise
  Downloading https://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.img...

  No image exists for this release/architecture

  [regression potential]

  very little, as this is a simple change and using precise or trusty
  with the script does not work at all currrently.  any regression would
  be around downloading the ubuntu-cloud image.

  [other info]

  this does not affect cosmic or earlier, as the precise/trusty removal
  was added in version 5.6 while those releases have earlier versions
  and still contain support for precise/trusty images in autopkgtest-
  buildvm-ubuntu-cloud.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1822331/+subscriptions