This bug was fixed in the package autopkgtest - 5.38ubuntu1~22.04.1
---------------
autopkgtest (5.38ubuntu1~22.04.1) jammy; urgency=medium
* SRU to Jammy (LP: #2071609)
-- Florent 'Skia' Jacquet <florent.jacq...@canonical.com> Fri, 11 Oct
2024 12:38:02 +0100
** Changed in: autopkgtest (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
Matching subscriptions: ubuntu-qa-bugs
https://bugs.launchpad.net/bugs/2075166
Title:
autopkgtest-buildvm-ubuntu-cloud hangs indefinitely with Jammy VM
Status in autopkgtest package in Ubuntu:
Fix Released
Status in autopkgtest source package in Jammy:
Fix Released
Status in autopkgtest source package in Noble:
Fix Committed
Bug description:
[ Impact ]
`autopkgtest-buildvm-ubuntu-cloud` is unable to produce a Jammy VM image,
because it hangs forever.
This is caused by the configuration of the `keyboard-configuration` package,
that prompts the user while the VM is not interactive.
The bug is fixed upstream:
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/384
The fix was to set `DEBIAN_FRONTEND=noninteractive` in the environment.
[ Test plan ]
autopkgtest-buildvm-ubuntu-cloud -a amd64 -r jammy -v
This command hangs, and the last printed line is `Setting up keyboard-
configuration`.
[ Where problems could occur ]
With the `DEBIAN_FRONTEND=noninteractive` variable set, packages will start
to use their default configuration instead of prompting the user. Those default
could be broken for an autopkgtest usage, but on the other hand, prompting
doesn't work either. Still, without the prompt hanging, it will be harder to
detect that some packages wanted to be configured, and further investigation
could be harder.
Despite that, I still think not prompting the user, and proceeding with a
working automated installation is preferable than not having the VM image in
the first place.
Also, this bugfix only impacts `autopkgtest-buildvm-ubuntu-cloud`.
It's not something buried deep in some shared code that could impact
other parts of the software, meaning it should have very limited
impact.
[ Other info ]
Thanks @zyga for reporting, and @simpoir for first pointing out the
missing debconf frontend.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2075166/+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
