Verification of noble, questing, plucky, resolute: ==================================================
Not required since its not affected (go >= 2.21). ** Description changed: [SRU] 2.73: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2132084 [ Impact ] Lastest snapd breaks LXD nested in a LXD container due to the daemon.activate script in lxd failing during install because of recent apparmor behavior changes that means snap-confine apparmor profile prevents access to passed fd associated with standard out used by the script. [ Test Plan ] - 1. Reproduce with snapd snap < 2.73 + 1. Reproduce with snapd deb < 2.73 - Use hwe kernel, 6.14.0-33-generic - install lxd: snap install --channel=5.21/stable lxd - Expect: snap.lxd.activate.service] failed with exit status 1: stderr - 2. Prove fixed with snapd snap 2.73 + 2. Prove fixed with snapd deb 2.73 - Use hwe kernel, 6.14.0-33-generic - install lxd: snap install --channel=5.21/stable lxd - Expect: snap.lxd.activate.service does not exit with error, and installation completes. ---original--- The new snapd deb in -proposed for Ubuntu 22.04 breaks running LXD nested in a LXD container resulting in root@j0:~# sudo snap install --channel=5.21/stable lxd error: cannot perform the following tasks: - Start snap "lxd" (35624) services (systemctl command [start snap.lxd.activate.service] failed with exit status 1: stderr: Job for snap.lxd.activate.service failed because the control process exited with error code. See "systemctl status snap.lxd.activate.service" and "journalctl -xeu snap.lxd.activate.service" for details.) Can be reproduced with $ multipass launch noble --name test -d 10G test$ snap install --channel=5.21/stable lxd test$ sudo lxd init --auto test$ lxc launch ubuntu:j j0 -c security.nesting=true test$ lxc shell j0 j0$ sudo snap remove --purge lxd j0$ cat <<EOF >/etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe EOF j0$ apt update ; apt upgrade j0$ snap install --channel=5.21/stable lxd We only see this on noble with kernel 6.14 when running Ubuntu 22.04 containers. Running the host with jammy and older kernels does not show the same problem. ** Description changed: [SRU] 2.73: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2132084 [ Impact ] Lastest snapd breaks LXD nested in a LXD container due to the daemon.activate script in lxd failing during install because of recent apparmor behavior changes that means snap-confine apparmor profile prevents access to passed fd associated with standard out used by the script. + + Only jammy is affected (go < 1.21) + See https://bugs.launchpad.net/snapd/+bug/2127244/comments/20 + [ Test Plan ] 1. Reproduce with snapd deb < 2.73 - Use hwe kernel, 6.14.0-33-generic - install lxd: snap install --channel=5.21/stable lxd - Expect: snap.lxd.activate.service] failed with exit status 1: stderr 2. Prove fixed with snapd deb 2.73 - Use hwe kernel, 6.14.0-33-generic - install lxd: snap install --channel=5.21/stable lxd - Expect: snap.lxd.activate.service does not exit with error, and installation completes. ---original--- The new snapd deb in -proposed for Ubuntu 22.04 breaks running LXD nested in a LXD container resulting in root@j0:~# sudo snap install --channel=5.21/stable lxd error: cannot perform the following tasks: - Start snap "lxd" (35624) services (systemctl command [start snap.lxd.activate.service] failed with exit status 1: stderr: Job for snap.lxd.activate.service failed because the control process exited with error code. See "systemctl status snap.lxd.activate.service" and "journalctl -xeu snap.lxd.activate.service" for details.) Can be reproduced with $ multipass launch noble --name test -d 10G test$ snap install --channel=5.21/stable lxd test$ sudo lxd init --auto test$ lxc launch ubuntu:j j0 -c security.nesting=true test$ lxc shell j0 j0$ sudo snap remove --purge lxd j0$ cat <<EOF >/etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe EOF j0$ apt update ; apt upgrade j0$ snap install --channel=5.21/stable lxd We only see this on noble with kernel 6.14 when running Ubuntu 22.04 containers. Running the host with jammy and older kernels does not show the same problem. ** Tags added: verification-done-resolute ** Tags removed: verification-needed-noble verification-needed-plucky verification-needed-questing ** Tags added: verification-done-noble verification-done-plucky verification-done-questing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127244 Title: Nested LXD is broken with snapd 2.71+ubuntu22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2127244/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
