Performing the verification for Jammy.
First we reproduce the bug:
$ apt policy autopkgtest
autopkgtest:
Installed: 5.32ubuntu3~22.04.1
Candidate: 5.32ubuntu3~22.04.1
Version table:
5.37ubuntu3~22.04.1 400
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages
*** 5.32ubuntu3~22.04.1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
100 /var/lib/dpkg/status
5.20 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
$ autopkgtest-build-lxd ubuntu-minimal:noble
Creating autopkgtest-prepare-2fl
Starting autopkgtest-prepare-2fl
Created symlink /etc/systemd/system/serial-getty@getty.service → /dev/null.
Container finished booting. Distribution Ubuntu, release noble, architecture
amd64
Running setup script /usr/share/autopkgtest/setup-commands/setup-testbed...
sh: Attempting to set up Debian/Ubuntu apt sources automatically
Failed to auto-detect apt mirror; set $MIRROR explicitly
The bug is successfully replicated.
Now we verify the fix.
$ apt policy autopkgtest
autopkgtest:
Installed: 5.37ubuntu3~22.04.1
Candidate: 5.37ubuntu3~22.04.1
Version table:
*** 5.37ubuntu3~22.04.1 400
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages
100 /var/lib/dpkg/status
5.32ubuntu3~22.04.1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
5.20 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
$ autopkgtest-build-lxd ubuntu-minimal:noble
Creating autopkgtest-prepare-UAV
Starting autopkgtest-prepare-UAV
Created symlink /etc/systemd/system/serial-getty@getty.service → /dev/null.
Issuing reboot (current boot id: f4927f2a-8daf-4a4e-9dfd-7d1fab25303b)
Reboot successful (current boot id: c53c28cd-3f19-496e-b9e9-516f79b057d7)
Container finished booting. Distribution Ubuntu, release noble, architecture
amd64
Running setup script /usr/share/autopkgtest/setup-commands/setup-testbed...
(truncated for brevity)
Instance published with fingerprint:
d88a89f2becf35752df7c64fa3978a8c2a1cb0ff1e8219a4e5827c50eeba022a
So lxd can successfully build and publish the container in the new
version of autopkgtest.
This concludes the verification for Jammy.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
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/2052639
Title:
deb822 sources are not supported (was: cannot create a local noble lxd
runner)
Status in autopkgtest package in Ubuntu:
Fix Released
Status in autopkgtest source package in Jammy:
Fix Committed
Bug description:
[Impact]
Noble was the first Ubuntu release that introduced deb822 only sources.
However,
this required support for that in autopkgtest.
[Test case]
$ autopkgtest-build-lxd ubuntu-daily:oracular
$ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble
$ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r oracular
[Fix]
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/287
This was release in autopkgtest 5.34, currently in the process of being SRU'd
to
Jammy in bug #2071609.
[Regression potential]
The current SRU has a lot of unrelated changes. While this increases the
chances of regression, this also come with a broader test suite, increasing
test
coverage, and so regressions should only happen in corner-cases, hopefully
less
important as the current lack of deb822 feature.
[Original bug report]
Hi there,
On current mantic, I cannot use autopkgtest-build-lxd to create a
noble LXD runner:
$ autopkgtest-build-lxd ubuntu-daily:noble
Detected local apt proxy, using http://10.235.222.1:3142 as container proxy
Creating autopkgtest-prepare-nDq
Starting autopkgtest-prepare-nDq
Created symlink /etc/systemd/system/serial-getty@getty.service → /dev/null.
Container finished booting. Distribution Ubuntu, release noble, architecture
amd64
Running setup script /usr/share/autopkgtest/setup-commands/setup-testbed...
awk: fatal: cannot open file `/etc/apt/sources.list' for reading: No such
file or directory
sh: Attempting to set up Debian/Ubuntu apt sources automatically
Failed to auto-detect apt mirror; set $MIRROR explicitly
I'm guessing this is related to deb822?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: autopkgtest 5.28ubuntu1 [modified: usr/bin/autopkgtest-build-lxd]
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Wed Feb 7 15:33:18 2024
InstallationDate: Installed on 2021-07-05 (947 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: autopkgtest
UpgradeStatus: Upgraded to mantic on 2023-09-13 (147 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2052639/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
