## PENDING SRU / REGRESSION EXPLANATIONS ** All the current systemd (trusty) autopktest failure are not related to the current SRU. Seems like they are failing for a while now and should be considered as known test failure already.
Regression in autopkgtest for network-manager (ppc64el): test log - Always fails the same way since at least "systemd/204-5ubuntu20.17" : http://autopkgtest.ubuntu.com/packages/n/network-manager/trusty/ppc64el Regression in autopkgtest for linux-lts-wily (armhf): test log - Always timeout the same way since at least "systemd/204-5ubuntu20.17" : http://autopkgtest.ubuntu.com/packages/l/linux-lts-wily/trusty/armhf Regression in autopkgtest for linux-lts-vivid (ppc64el): test log - ERROR: running version does not match source package Regression in autopkgtest for linux-lts-vivid (i386): test log - ERROR: running version does not match source package Regression in autopkgtest for linux-lts-vivid (amd64): test log - ERROR: running version does not match source package Regression in autopkgtest for linux-lts-vivid (armhf): test log - Always fails the same way since at least "systemd/204-5ubuntu20.14" : http://autopkgtest.ubuntu.com/packages/l/linux-lts-vivid/trusty/armhf Regression in autopkgtest for linux-lts-utopic (ppc64el): test log - ERROR: running version does not match source package Regression in autopkgtest for linux-lts-utopic (i386): test log - ERROR: running version does not match source package Regression in autopkgtest for linux-lts-utopic (amd64): test log - ERROR: running version does not match source package Regression in autopkgtest for linux-lts-utopic (armhf): test log - Always fails the same way since at least "systemd/204-5ubuntu20.15" : http://autopkgtest.ubuntu.com/packages/l/linux-lts-utopic/trusty/armhf Regression in autopkgtest for linux-lts-xenial (ppc64el): test log - ERROR: running version does not match source package Regression in autopkgtest for linux-lts-xenial (i386): test log - ERROR: running version does not match source package Regression in autopkgtest for linux-lts-xenial (amd64): test log - ERROR: running version does not match source package Regression in autopkgtest for linux-lts-xenial (armhf): test log - Always fails the same way since "systemd/204-5ubuntu20.19" : http://autopkgtest.ubuntu.com/packages/l/linux-lts-xenial/trusty/armhf ** ERROR: running version does not match source package ** Source Package Version: 3.16.0-77.99~14.04.1 Running Kernel Version: 3.13.0-133.182 - Eric ** Description changed: [Impact] Installing snaps is not possible on Ubuntu 14.04 when having /var on its own partition, whether its LVM or not. The issue is with the core snap being unable to mount: The error with /var isolated and using LVM: root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) The error with /var isolated but without using LVM: root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service' for details. ) The same error happens if I try to install the hello-world snap (with LVM in this example): root@ubuntu:~# snap install hello-world error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) I cannot reproduce the issue in Ubuntu 16.04. I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image which doesn't isolate /var on its own partition. I tried adding a secondary disk to that cloud image VM and create a dummy VG and LV, but couldn't reproduce the issue. Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with only a / partition and swap. [Test Case] # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and configure /, /var and swap on their own partitions (with LVM or not, the issue happens in both situations). root@ubuntu:~# lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert rootvol vg00 -wi-ao--- 3.72g swap vg00 -wi-ao--- 3.72g varvol vg00 -wi-ao--- 3.72g root@ubuntu:~# df -h Filesystem Size Used Avail Use% Mounted on udev 484M 4.0K 484M 1% /dev tmpfs 100M 988K 99M 1% /run /dev/dm-0 3.7G 1.7G 1.8G 49% / none 4.0K 0 4.0K 0% /sys/fs/cgroup none 5.0M 0 5.0M 0% /run/lock none 497M 0 497M 0% /run/shm none 100M 0 100M 0% /run/user /dev/mapper/vg00-varvol 3.7G 716M 2.8G 21% /var # Upgrade system, install snapd and reboot root@ubuntu:~# apt update root@ubuntu:~# apt upgrade -y root@ubuntu:~# apt install -y snapd root@ubuntu:~# reboot # After reboot, check kernel version and try to install the canonical- livepatch snap: root@ubuntu:~# uname -a Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu:~# snap list No snaps are installed yet. Try "snap install hello-world". root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) [Regression Potential] - Unit file has been added to systemd, could cause an error in some units initialization. Since systemd is not used as "init" system for Trusty, this is minor regression. - Could break all systemd units depending (After=/Wants=) systemd-fsck@.service but they are already broken. ** A "pre-SRU" test package provided in Tinoco's PPA has been also intensively tested with success, which bring even more confidence for this change. Note that the same level/quality of testing will be performed one more time when the package will be found in trusty- proposed. ** * Manual autopkgtest againts the systemd .dsc file : adt-run [12:31:42]: @@@@@@@@@@@@@@@@@@@@ summary timedated PASS hostnamed PASS localed-locale PASS localed-x11-keymap PASS logind PASS api PASS + * About the autopkgtest regressions found : + https://bugs.launchpad.net/snapd/+bug/1718966/comments/14 [Other Info] [Original Description] Installing snaps is not possible on Ubuntu 14.04 when having /var on its own partition, whether its LVM or not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1718966 Title: Cannot install snaps on Ubuntu 14.04 with /var on its own partition Status in snapd: Invalid Status in systemd package in Ubuntu: Invalid Status in systemd source package in Trusty: Fix Committed Bug description: [Impact] Installing snaps is not possible on Ubuntu 14.04 when having /var on its own partition, whether its LVM or not. The issue is with the core snap being unable to mount: The error with /var isolated and using LVM: root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) The error with /var isolated but without using LVM: root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service' for details. ) The same error happens if I try to install the hello-world snap (with LVM in this example): root@ubuntu:~# snap install hello-world error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) I cannot reproduce the issue in Ubuntu 16.04. I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image which doesn't isolate /var on its own partition. I tried adding a secondary disk to that cloud image VM and create a dummy VG and LV, but couldn't reproduce the issue. Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with only a / partition and swap. [Test Case] # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and configure /, /var and swap on their own partitions (with LVM or not, the issue happens in both situations). root@ubuntu:~# lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert rootvol vg00 -wi-ao--- 3.72g swap vg00 -wi-ao--- 3.72g varvol vg00 -wi-ao--- 3.72g root@ubuntu:~# df -h Filesystem Size Used Avail Use% Mounted on udev 484M 4.0K 484M 1% /dev tmpfs 100M 988K 99M 1% /run /dev/dm-0 3.7G 1.7G 1.8G 49% / none 4.0K 0 4.0K 0% /sys/fs/cgroup none 5.0M 0 5.0M 0% /run/lock none 497M 0 497M 0% /run/shm none 100M 0 100M 0% /run/user /dev/mapper/vg00-varvol 3.7G 716M 2.8G 21% /var # Upgrade system, install snapd and reboot root@ubuntu:~# apt update root@ubuntu:~# apt upgrade -y root@ubuntu:~# apt install -y snapd root@ubuntu:~# reboot # After reboot, check kernel version and try to install the canonical- livepatch snap: root@ubuntu:~# uname -a Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu:~# snap list No snaps are installed yet. Try "snap install hello-world". root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) [Regression Potential] - Unit file has been added to systemd, could cause an error in some units initialization. Since systemd is not used as "init" system for Trusty, this is minor regression. - Could break all systemd units depending (After=/Wants=) systemd-fsck@.service but they are already broken. ** A "pre-SRU" test package provided in Tinoco's PPA has been also intensively tested with success, which bring even more confidence for this change. Note that the same level/quality of testing will be performed one more time when the package will be found in trusty- proposed. ** * Manual autopkgtest againts the systemd .dsc file : adt-run [12:31:42]: @@@@@@@@@@@@@@@@@@@@ summary timedated PASS hostnamed PASS localed-locale PASS localed-x11-keymap PASS logind PASS api PASS * About the autopkgtest regressions found : https://bugs.launchpad.net/snapd/+bug/1718966/comments/14 [Other Info] [Original Description] Installing snaps is not possible on Ubuntu 14.04 when having /var on its own partition, whether its LVM or not. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1718966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp