snapd 2.27 comes with "Nice=-5" in its systemd unit. This prevents snapd from starting in LXD containers as was reported previously upstream here: https://bugs.launchpad.net/snapd/+bug/1709536
Releasing this SRU would break snapd in every LXD container and also cause boot issues. I'm therefore marking this SRU as failed for all releases. root@xenial:~# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libmspack0 logrotate pollinate python3-update-manager snapd ubuntu-core-launcher update-manager-core 7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 10.8 MB of archives. After this operation, 8461 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 ubuntu-core-launcher amd64 2.27.2 [1562 B] Get:2 http://us.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 snapd amd64 2.27.2 [10.7 MB] Get:3 http://us.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 logrotate amd64 3.8.7-2ubuntu2.16.04.2 [37.7 kB] Get:4 http://us.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 python3-update-manager all 1:16.04.9 [31.9 kB] Get:5 http://us.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 update-manager-core all 1:16.04.9 [5330 B] Get:6 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libmspack0 amd64 0.5-1ubuntu0.16.04.1 [37.0 kB] Get:7 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 pollinate all 4.25-0ubuntu1~16.04.1 [11.6 kB] Fetched 10.8 MB in 1s (5537 kB/s) (Reading database ... 25507 files and directories currently installed.) Preparing to unpack .../ubuntu-core-launcher_2.27.2_amd64.deb ... Unpacking ubuntu-core-launcher (2.27.2) over (2.25) ... Preparing to unpack .../snapd_2.27.2_amd64.deb ... Warning: Stopping snapd.service, but it can still be activated by: snapd.socket Unpacking snapd (2.27.2) over (2.25) ... Preparing to unpack .../logrotate_3.8.7-2ubuntu2.16.04.2_amd64.deb ... Unpacking logrotate (3.8.7-2ubuntu2.16.04.2) over (3.8.7-2ubuntu2.16.04.1) ... Preparing to unpack .../python3-update-manager_1%3a16.04.9_all.deb ... Unpacking python3-update-manager (1:16.04.9) over (1:16.04.8) ... Preparing to unpack .../update-manager-core_1%3a16.04.9_all.deb ... Unpacking update-manager-core (1:16.04.9) over (1:16.04.8) ... Preparing to unpack .../libmspack0_0.5-1ubuntu0.16.04.1_amd64.deb ... Unpacking libmspack0:amd64 (0.5-1ubuntu0.16.04.1) over (0.5-1) ... Preparing to unpack .../pollinate_4.25-0ubuntu1~16.04.1_all.deb ... Unpacking pollinate (4.25-0ubuntu1~16.04.1) over (4.23-0ubuntu1~16.04.1) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up snapd (2.27.2) ... Installing new version of config file /etc/apparmor.d/usr.lib.snapd.snap-confine.real ... Job for snapd.service failed because the control process exited with error code. See "systemctl status snapd.service" and "journalctl -xe" for details. snapd.service couldn't start. Setting up ubuntu-core-launcher (2.27.2) ... Setting up logrotate (3.8.7-2ubuntu2.16.04.2) ... Setting up python3-update-manager (1:16.04.9) ... Setting up update-manager-core (1:16.04.9) ... Setting up libmspack0:amd64 (0.5-1ubuntu0.16.04.1) ... Setting up pollinate (4.25-0ubuntu1~16.04.1) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... root@xenial:~# systemctl cat snapd # /lib/systemd/system/snapd.service [Unit] Description=Snappy daemon Requires=snapd.socket [Service] Nice=-5 OOMScoreAdjust=-900 ExecStart=/usr/lib/snapd/snapd EnvironmentFile=-/etc/environment Restart=always Type=notify [Install] WantedBy=multi-user.target root@xenial:~# snap list error: cannot list snaps: cannot communicate with server: Get http://localhost/v2/snaps: dial unix /run/snapd.socket: connect: connection refused root@xenial:~# root@xenial:~# journalctl -u snapd -n 10 -- Logs begin at Thu 2017-08-17 19:48:36 UTC, end at Thu 2017-08-17 19:51:12 UTC. -- Aug 17 19:51:11 xenial systemd[1]: Stopped Snappy daemon. Aug 17 19:51:11 xenial systemd[1]: Starting Snappy daemon... Aug 17 19:51:11 xenial systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 17 19:51:11 xenial systemd[1]: Failed to start Snappy daemon. Aug 17 19:51:11 xenial systemd[1]: snapd.service: Unit entered failed state. Aug 17 19:51:11 xenial systemd[1]: snapd.service: Failed with result 'exit-code'. Aug 17 19:51:12 xenial systemd[1]: snapd.service: Service hold-off time over, scheduling restart. Aug 17 19:51:12 xenial systemd[1]: Stopped Snappy daemon. Aug 17 19:51:12 xenial systemd[1]: snapd.service: Start request repeated too quickly. Aug 17 19:51:12 xenial systemd[1]: Failed to start Snappy daemon. root@xenial:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703798 Title: [SRU] 2.27.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1703798/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
