Updated the SRU test plan to use a Noble LXC container instead of Focal. Focal is EOL, and this surfaced a bug in debootstrap that I will report separately. Besides the container release change, the test plan is exactly the same as it was before this update.
In short, during LXC container creation, signature validation fails as debootstrap is unable to locate the signing key for Focal. This is not related to the LXC package update as part of this bug, but rather Focal going EOL since I did the PPA test and surfacing an issue in debootstrap. Thus this is not a blocker for this SRU. --- Executed the (updated) test plan on the following package versions: * noble * unpatched: 1:5.0.3-2ubuntu7.1 (updates) * fixed: 1:5.0.3-2ubuntu7.2 (proposed) * oracular * unpatched: 1:6.0.1-1ubuntu1.1 (updates) * fixed: 1:6.0.1-1ubuntu1.2 (proposed) * plucky * unpatched: 1:6.0.3-1 (release) * fixed: 1:6.0.3-1ubuntu1 (proposed) Steps 7-8 followed the "enable proposed" steps as linked. After each install/upgrade, installed version verified with `dpkg -l lxc`. All steps 1-21 were followed. The outcomes of all steps were as expected, where the unpatched versions reproduced the issue, and the fixed versions no longer exhibited the incorrect behaviour. Test environment is Ubuntu noble, oracular, plucky arm64 virtual machines running on a macOS 15.5 host under Parallels Desktop 20.4.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2109890 Title: [SRU] lxc: container_ttys env var not populated, leading to broken lxc-console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2109890/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
