canonical-ubuntu-qa team mailing list archive

[Paride Legovini <2020188@xxxxxxxxxxxxxxxxxx>]

@Tim you mentioned you don't hit the bug on your Jammy system
(autopkgtest 5.20ubuntu1), however I hit it on Jammy too. This is in a
Jammy LXD container:

---------------------------------------------
root@paride-j:~# lsb_release -c
Codename:	jammy

root@paride-j:~# dpkg -l | grep autopkgtest
ii  autopkgtest                     5.20ubuntu1

root@paride-j:~# autopkgtest-buildvm-ubuntu-cloud -v -r jammy
Downloading https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img...
682.8/686.2 MB (100%)                 
Download failed!
---------------------------------------------

If this is indeed the case, then maybe something changed on the server
side (cloud-images.ubuntu.com), and we don't really have a
bug+regression in autopkgtest?

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

Title:
  autopkgtest-buildvm-ubuntu-cloud exits with message "Download failed!"

Status in autopkgtest package in Ubuntu:
  Confirmed
Status in autopkgtest source package in Focal:
  New
Status in autopkgtest source package in Jammy:
  New
Status in autopkgtest source package in Kinetic:
  New
Status in autopkgtest source package in Lunar:
  New

Bug description:
  This happens for me with version 5.28ubuntu1 of autopkgtest on my Lunar system. The failure happens as follows:
  The script downloads the file, reaches 100% download capacity and then exits with the message "Download failed!", shown below:
  ```
  andersson123@duckstation7:~/canonical/code/autopkgtest/tools$ sudo ./autopkgtest-buildvm-ubuntu-cloud -a amd64 -r mantic -s 10G
  [sudo] password for andersson123: 
  WARNING: cannot determine development release, falling back to latest stable
  Downloading https://cloud-images.ubuntu.com/mantic/current/mantic-server-cloudimg-amd64.img...
  825.3/829.5 MB (100%)
  Download failed!
  ```
  Upon further inspection, I discovered the conditional statement responsible for this is here:
  https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/tools/autopkgtest-buildvm-ubuntu-cloud#L204

  I added a print statement to show the http header, and the fields the if statement were searching for weren't in it:
  ```
  andersson123@duckstation7:~/canonical/code/autopkgtest/tools$ sudo ./autopkgtest-buildvm-ubuntu-cloud -a amd64 -r mantic -s 10G
  [sudo] password for andersson123: 
  WARNING: cannot determine development release, falling back to latest stable
  Downloading https://cloud-images.ubuntu.com/mantic/current/mantic-server-cloudimg-amd64.img...
  825.3/829.5 MB (100%)                 Date: Fri, 19 May 2023 11:17:42 GMT
  Server: Apache/2.4.29 (Ubuntu)
  Last-Modified: Fri, 19 May 2023 03:01:32 GMT
  ETag: "31710000-5fc03235dbb00"
  Accept-Ranges: bytes
  Content-Length: 829489152
  Connection: close

  Download failed!
  ```

  I then commented out this if statement, ran the script again and it
  succeeded to build the image without any problems, so I question the
  necessity of this if statement, although I haven't dug much deeper
  into the code to understand it.

  I then tried the same console command on my jammy system, with
  autopkgtest version 5.20ubuntu1. It succeeded without the same error.
  I then installed version 5.28ubuntu0.22.04.0 from jammy-proposed on my
  jammy system, ran the same command and then got the same error as on
  my lunar system.

  I tried the command with different releases, i.e. building a jammy,
  kinetic, lunar and mantic .img file, but it failed for all of these,
  which leads me to believe it'd fail for all releases.

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