[Bug 2125338] Re: [SRU] Cannot fetch files from MAAS stream on autopkgtest runner

[Timo Aaltonen]

Hello Mate, or anyone else affected,

Accepted ubuntu-boot-test into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/ubuntu-
boot-test/2.1~22.04 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-boot-test (Ubuntu Jammy)
       Status: New => Fix Committed

** Tags removed: verification-done
** Tags added: verification-needed verification-needed-jammy

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

Title:
  [SRU] Cannot fetch files from MAAS stream on autopkgtest runner

Status in ubuntu-boot-test package in Ubuntu:
  Fix Released
Status in ubuntu-boot-test source package in Jammy:
  Fix Committed
Status in ubuntu-boot-test source package in Noble:
  Fix Released
Status in ubuntu-boot-test source package in Plucky:
  Fix Released
Status in ubuntu-boot-test source package in Questing:
  Fix Released

Bug description:
  [ Impact ]

  IS changed some proxy rules so that we can no longer download MAAS
  bootloader artifacts for testing. E.g.

  ```
  1117s autopkgtest [14:10:02]: test uefi-maas-amd64: ubuntu_boot_test_run uefi_maas -r $(lsb_release --codename --short) -a amd64
  1117s autopkgtest [14:10:02]: test uefi-maas-amd64: [-----------------------
  1119s Traceback (most recent call last):
  1119s   File "/usr/bin/ubuntu_boot_test_run", line 45, in <module>
  1119s     globals()[f"cmd_{args.command}"].execute(args)
  1119s     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
  1119s   File "/usr/lib/python3/dist-packages/ubuntu_boot_test/cmd_uefi_maas.py", line 101, in execute
  1119s     fetch_maas_loaders()
  1119s     ~~~~~~~~~~~~~~~~~~^^
  1119s   File "/usr/lib/python3/dist-packages/ubuntu_boot_test/cmd_uefi_maas.py", line 83, in fetch_maas_loaders
  1119s     stream = json.loads(fetch_file(MAAS_STABLE_STREAM_URL))
  1119s                         ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
  1119s   File "/usr/lib/python3/dist-packages/ubuntu_boot_test/util.py", line 104, in fetch_file
  1119s     assert resp.status_code == 200, "Failed to fetch file"
  ```

  This is unfortunate because it is making our autopkgtest baselines
  regress. We can do most of the useful netboot validation without.

  This has been broken for too long, and it seems like waiting on IS
  isn't going to solve it in a reasonable timeframe, so I am going to
  remove the subtests that download files from the MAAS stream (and
  openSUSE images) as a regressed ubuntu-boot-test baseline is
  unacceptable.

  [ Test Plan ]

  All we need to do is make sure that the new upload's autopkgtests pass
  and review the log for anomalies.

  [ Where problems could occur ]

  It could in theory cause uncaught regressions in cross-version,
  network based GRUB chainload scenarios, but this is still going to be
  extremely unlikely because comprehensive netboot tests will remain in
  place, just not ones that uses artifacts directly from the MAAS
  stream.

  [ Other Info ]

  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-boot-test/+bug/2125338/+subscriptions