This bug was fixed in the package livecd-rootfs - 2.765.34
---------------
livecd-rootfs (2.765.34) jammy; urgency=medium
* Remove comments in the debian/control dependencies as it was causing the
package build to fail.
livecd-rootfs (2.765.33) jammy; urgency=medium
[ Steve Langasek ]
* Use losetup instead of kpartx to resolve race conditions in riscv64
image builds. LP: #2045797.
[ Utkarsh Gupta ]
* unminimize: Use lxd-installer to install LXD itself (LP: #2036725)
livecd-rootfs (2.765.32) jammy; urgency=medium
[ Heinrich Schuchardt ]
* arm: fix console parameter for ARM cloud-images (LP: #2036730)
livecd-rootfs (2.765.31) jammy; urgency=medium
[ John Chittum ]
* fix: add 6.5 kernel apparmor features to livecd-rootfs based on
features of 6.5 in ubuntu/mantic. This will roll as HWE. (LP: #2037567)
livecd-rootfs (2.765.30) jammy; urgency=medium
* Enable snap preseeding with ppc64el images where /boot/vmlinux is used
instead of /boot/vmlinuz. (LP: #2038957)
livecd-rootfs (2.765.29) jammy; urgency=medium
[ Steve Langasek ]
* The chroot tmpfs mount should only be /var/lib/apt/lists, not
/var/lib/apt; the latter breaks changes to /var/lib/apt/extended_states.
(LP: #2036195).
livecd-rootfs (2.765.28) jammy; urgency=medium
* Fix unminimize to correctly list packages. (LP: #1996489)
* Install LXD snap from stable/ubuntu-<version> channel. (LP: #2036725)
livecd-rootfs (2.765.27) jammy; urgency=medium
[ Thomas Bechtold ]
* Do not modify /etc/ssh/sshd_config for ubuntu-cpc
project builds (LP: #1968873)
-- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com> Mon, 15 Jan
2024 16:41:18 +0100
** Changed in: livecd-rootfs (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.
https://bugs.launchpad.net/bugs/2036730
Title:
autopkgtest ignores --architecture flag
Status in autopkgtest package in Ubuntu:
Incomplete
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in autopkgtest source package in Focal:
New
Status in livecd-rootfs source package in Focal:
Won't Fix
Status in autopkgtest source package in Jammy:
New
Status in livecd-rootfs source package in Jammy:
Fix Released
Status in autopkgtest source package in Lunar:
New
Status in livecd-rootfs source package in Lunar:
Fix Released
Status in autopkgtest source package in Mantic:
New
Status in livecd-rootfs source package in Mantic:
Fix Released
Bug description:
Description
-----------
The cloud images produced by livecd-rootfs do not properly configure the tty
for armhf and subsequently the terminal output is not available.
Test Case
---------
1) Run `autopkgtest-buildvm-ubuntu-cloud -v --arch armhf --release mantic`
substituting the release name as appropriate
2) Observe the last console message `EFI stub: Exiting boot services...`
With a cloud image build with the livecd-rootfs version in -proposed
you'll see much more output from `autopkgtest-buildvm-ubuntu-cloud`
including cloud-init configuring the system.
Regression Potential
--------------------
The serial console is being set to ttyS0 differently that it was for
architectures other than arm64 or armhf. However, this has been in place in
noble for an extended period of time and has not cause any regressions for
those architectures.
Original Description
--------------------
On an arm64 as well as on amd64 I saw this behavior:
$ autopkgtest-buildvm-ubuntu-cloud -v --arch armhf --release mantic
$ autopkgtest -U --apt-pocket=proposed -a armhf -s *.dsc -- qemu
autopkgtest-mantic-armhf.img
autopkgtest [13:18:32]: starting date and time: 2023-09-20 13:18:32+0200
autopkgtest [13:18:32]: version 5.28ubuntu1
autopkgtest [13:18:32]: host mcbin; command line: /usr/bin/autopkgtest -U
--apt-pocket=proposed -a armhf -s forensics-all_3.47.dsc -- qemu
autopkgtest-mantic-armhf.img
qemu-system-aarch64: terminating on signal 15 from pid 3520 (/usr/bin/python3)
<VirtSubproc>: failure: timed out waiting for 'login prompt on serial console'
autopkgtest [13:19:33]: ERROR: testbed failure: unexpected eof from the
testbed
When trying to boot into the image on an arm64 system with
qemu-system-aarch64 \
-machine virt -accel kvm -m 4G -smp 4 -cpu host,aarch64=off -nographic \
-object rng-random,filename=/dev/urandom,id=rng0 \
-device virtio-rng-pci,rng=rng0,id=rng-device0 \
-drive
if=pflash,format=raw,unit=0,read-only=on,file=/usr/share/AAVMF/AAVMF32_CODE.fd \
-device virtio-net-pci,netdev=eth0 \
-netdev user,id=eth0,hostfwd=tcp::8022-:22 \
-drive file=autopkgtest-mantic-armhf.img,if=virtio,format=qcow2
the last messages displayed are
EFI stub: Booting Linux Kernel...
EFI stub: Entering in SVC mode with MMU enabled
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services...
qemu-system-aarch64 seems to be close to idling at less than 0.5 % CPU
load. So booting obviously stalled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2036730/+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
