sts-sponsors team mailing list archive

[Łukasz Zemczak <1822331@xxxxxxxxxxxxxxxxxx>]

With my release team member hat: since it's debatable whether this is a
feature or bugfix, even in the case of it being a feature I'd be +1 on
letting it in. Since it's only introducing series to the list, there
should be no regression potential that it could delay the release. So
feel free to upload it.

It might be also debatable if we need to support those series in
autopkgtest-buildvm-ubuntu-cloud, but as Dan and Eric said, with precise
being ESM and trusty joining in soon, it might make sense for them to
stick around. I don't think there are currently any automated britney
runs for packages in the precise ESM pocket, but I can still feel it
might be somewhat useful to run such tests locally before doing ESM
uploads.

-- 
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
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:
  Fix Committed

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