[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 204-5ubuntu20.25

---
systemd (204-5ubuntu20.25) trusty; urgency=medium

  * rules: introduce fsck@.service for snappy (LP: #1718966)

 -- Rafael David Tinoco   Mon, 02 Oct 2017
21:39:38 +

** Changed in: systemd (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
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 Released

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 

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Eric Desrochers]

** Tags removed: patch

-- 
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 Released

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
  timedatedPASS
  hostnamedPASS
  localed-locale   PASS
  localed-x11-keymap   PASS
  logind 

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Rafael David Tinoco]

Verifying...

http://pastebin.ubuntu.com/25753116/

After using -proposed version:

http://paste.ubuntu.com/25753146/

Considering this fixed. Verified!

** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty

-- 
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 

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Eric Desrochers]

## 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--- 

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Łukasz Zemczak]

Hello David, or anyone else affected,

Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.25 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu)
   Status: In Progress => Invalid

** Changed in: systemd (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-trusty

-- 
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 

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Rafael David Tinoco]

After fixing this BUG (for canonical-livepatch snap to work, but being
affected by broken systemd in Trusty due to the lack of systemd-
fsck@.service unit file, I'm facing the following opened BUG:
https://bugs.launchpad.net/snapd/+bug/1721518 for canonical-livepatch
(or any other snap) to work).

-- 
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:
  In Progress
Status in systemd source package in Trusty:
  In Progress

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 

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Eric Desrochers]

** 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
+ timedatedPASS
+ hostnamedPASS
+ localed-locale   PASS
+ localed-x11-keymap   PASS
+ logind   PASS
+ api  PASS
+ 
+ 
  [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.

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Eric Desrochers]

Sponsored, the package is now in the Trusty upload queue, waiting for
the SRU verification team to approve the package to start building in
trusty-proposed.

- Eric

** Tags removed: sts-sponsor
** Tags added: sts-sponsor-done sts-sru-needed

** 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. **
+ 
  [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:

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[David Coronel]

I tested the fix from ppa:inaddy/lp1718966 and I am now able to install
snaps on my two test systems without using the /etc/fstab workaround,
one with LVM and one without. Both systems have /var isolated. Thanks!

-- 
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:
  In Progress
Status in systemd source package in Trusty:
  In Progress

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.

  [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] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Rafael David Tinoco]

** 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.
  
  [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:
  In Progress
Status in systemd source package in Trusty:
  In Progress

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 

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Eric Desrochers]

** 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.
  
- 
- Steps to reproduce:
- ===
+ [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 
+ 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
- tmpfs100M  988K   99M   1% /run
- /dev/dm-03.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
- 
+ 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:
+ # 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]
+ 
+ 
+ [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.

** Changed in: systemd (Ubuntu Trusty)
   Importance: Undecided => Medium

-- 
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:
  

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Rafael David Tinoco]

Meanwhile I have created a PPA containing the fix for all those affected
users:

https://launchpad.net/~inaddy/+archive/ubuntu/lp1718966

$ sudo add-apt-repository ppa:inaddy/lp1718966
$ sudo apt-get update
$ sudo apt-get dist-upgrade

Is likely enough for you to have a temporary fix.

-- 
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:
  In Progress
Status in systemd source package in Trusty:
  In Progress

Bug description:
  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.

  
  Steps to reproduce:
  ===

  # 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
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.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.
  )

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

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Ubuntu Foundations Team Bug Bot]

The attachment "trusty_systemd_204-5ubuntu20.25.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
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:
  In Progress
Status in systemd source package in Trusty:
  In Progress

Bug description:
  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.

  
  Steps to reproduce:
  ===

  # 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
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.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.
  )

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1718966/+subscriptions

-- 

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Rafael David Tinoco]

I've made a small change creating a unit file slightly different from
the one already present in systemd-204, considering different
dependencies for this usage (mounting/umounting volumes when upstart has
already taken part on it).

The result is here: http://pastebin.ubuntu.com/25663762/

As you can see, after installing the new packages, being proposed in
this fix, snapd can work again mounting all new squash filesystems it
depends on.

- Attaching the debdiff for SRU.
- Requesting SRU sponsoring.
- Will verify once it gets uploaded to -proposed.

** Patch added: "trusty_systemd_204-5ubuntu20.25.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718966/+attachment/4960880/+files/trusty_systemd_204-5ubuntu20.25.debdiff

** Tags added: sts sts-sponsor

-- 
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:
  In Progress
Status in systemd source package in Trusty:
  In Progress

Bug description:
  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.

  
  Steps to reproduce:
  ===

  # 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
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.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 

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Rafael David Tinoco]

Okay, so another quick workaround, now keeping the fsck enabled for the
volumes:

Create a file called "/lib/systemd/upstart/systemd-fsck@.service" with:


#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=File System Check on %f
Documentation=man:systemd-fsck@.service(8)
DefaultDependencies=no
BindsTo=%i.device
After=systemd-readahead-collect.service systemd-readahead-replay.service 
%i.device
Before=shutdown.target

[Service]
Type=oneshot
RemainAfterExit=no
ExecStart=/lib/systemd/systemd-fsck %f
StandardOutput=journal+console
TimeoutSec=0


and then do:

$ sudo ln -s /lib/systemd/upstart/systemd-fsck@.service 
/lib/systemd/upstart/multi-user.target.wants/systemd-fsck@.service
$ sudo systemctl daemon-reload

This will allow the mount units to work using systemd in Trusty:

inaddy@trustylivepatch:~$ sudo systemctl start teste.mount
inaddy@trustylivepatch:~$ df -kh | grep teste
/dev/sdb2   976M  1.3M  908M   1% /teste
inaddy@trustylivepatch:~$ sudo systemctl stop teste.mount
inaddy@trustylivepatch:~$ cat /etc/fstab| grep teste
LABEL=TESTE /teste ext4 defaults 0 1

While still having fsck enabled in /etc/fstab.

I'll provide a SRU patch for systemd in Trusty and it shall solve this
issue.

** Changed in: snapd
   Status: In Progress => Invalid

-- 
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:
  In Progress
Status in systemd source package in Trusty:
  In Progress

Bug description:
  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.

  
  Steps to reproduce:
  ===

  # 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
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.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

  
  

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[David Coronel]

I confirm the workaround works for me:

Before:

root@ubuntu:~# cat /etc/fstab
/dev/mapper/vg00-rootvol /   ext4errors=remount-ro 0   1
/dev/mapper/vg00-varvol /varext4defaults0   2
/dev/mapper/vg00-swap noneswapsw  0   0

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.
)


After:

root@ubuntu:~# cat /etc/fstab
/dev/mapper/vg00-rootvol /   ext4errors=remount-ro 0   1
/dev/mapper/vg00-varvol /varext4defaults0   0
/dev/mapper/vg00-swap noneswapsw  0   0

root@ubuntu:~# snap install hello-world
hello-world 6.3 from 'canonical' installed

root@ubuntu:~# snap install canonical-livepatch
canonical-livepatch 7 from 'canonical' installed

root@ubuntu:~# sudo canonical-livepatch enable 

root@ubuntu:~# canonical-livepatch status 
kernel: 4.4.0-96.119~14.04.1-generic
fully-patched: true
version: ""


Thanks Rafael!

-- 
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:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  In Progress

Bug description:
  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.

  
  Steps to reproduce:
  ===

  # 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
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.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 

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Rafael David Tinoco]

Ok so in systemd-204, in TRUSTY, you will find the following logic to
create the mount units:

- manager_loop
  - process-event (WATCH_MOUNT)
- mount_fd_event
  - mount_load_proc_self_mountinfo
- mount_add_one (if load_extras == true)
  - mount_add_extras
- mount_add_device_links

The last function will add: device/mount/socket/swap/path/requires/...
dependencies in the mount unit to be created. The first one "device" is
handled by "mount_add_device_links" and, according to logic:

if (p->passno > 0 &&
UNIT(m)->manager->running_as == SYSTEMD_SYSTEM) {
char *name;
Unit *fsck;
/* Let's add in the fsck service */

/* aka SPECIAL_FSCK_SERVICE */
name = unit_name_from_path_instance("systemd-fsck", p->what, 
".service");
if (!name)
return -ENOMEM;

If filesystem option passno is 0, it won't have the systemd-fsck unit as
a requirement, meaning that no error will be given, allowing the mount
unit, created by snappy, to work.



Check it out:

1)

## /etc/fstab

LABEL=LVROOT / ext4 errors=remount-ro 0 1
LABEL=LVVAR /var ext4 defaults 0 1
LABEL=TESTE /teste ext4 defaults 0 1

$ sudo 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-disk-by\x2dlabel-LVVAR.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-disk-by\x2dlabel-LVVAR.service' for details.

2)

## /etc/fstab

LABEL=LVROOT / ext4 errors=remount-ro 0 1
LABEL=LVVAR /var ext4 defaults 0 0
LABEL=TESTE /teste ext4 defaults 0 0

$ sudo snap install hello-world
hello-world 6.3 from 'canonical' installed



Now I'm checking why debian/rules in systemd-204 didn't include
fsck@.service files in the final .deb for "systemd" package. Possibly
this wasn't noticed because at the time systemd was running in Trusty,
it wasn't imagined that mount units would be managed by systemd (like
snappy is doing now). I'll check if adding the units for fsck (plus
having systemd-fsck binary, already there) is enough for the mount logic
to work.

For now, use the workaround above ^.

** Changed in: systemd (Ubuntu Trusty)
   Status: Confirmed => In Progress

** Changed in: snapd
   Status: Confirmed => In Progress

-- 
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:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  In Progress

Bug description:
  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.

  
  Steps to 

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Rafael David Tinoco]

** Changed in: systemd (Ubuntu Trusty)
 Assignee: (unassigned) => Rafael David Tinoco (inaddy)

-- 
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:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  Confirmed

Bug description:
  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.

  
  Steps to reproduce:
  ===

  # 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
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.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.
  )

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

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu Trusty)
   Status: New => Confirmed

-- 
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:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  Confirmed

Bug description:
  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.

  
  Steps to reproduce:
  ===

  # 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
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.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.
  )

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

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Eric Desrochers]

** Also affects: systemd (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
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:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  New

Bug description:
  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.

  
  Steps to reproduce:
  ===

  # 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
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.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.
  )

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

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Rafael David Tinoco]

I was also able to reproduce this, here are my notes for now:

## /etc/fstab

LABEL=LVROOT / ext4 errors=remount-ro 0 1
LABEL=LVVAR /var ext4 defaults 0 1
LABEL=TESTE /teste ext4 defaults 0 1

Right after boot:

inaddy@trustylivepatch:~$ systemctl list-units --all | grep fsck
systemd-...el-LVVAR.service error  inactive dead
systemd-fsck@dev-disk-by\x2dlabel-LVVAR.service
systemd-...el-TESTE.service error  inactive dead
systemd-fsck@dev-disk-by\x2dlabel-TESTE.service

This indicates that UPSTART is the one mounting the block devices, NOT
SYSTEMD using its mount units. SNAPS are mounting the SQUASH filesystems
using SYSTEMD UNITS, despite UPSTART scripts.

It is likely that this wasn't noticed, on systems mounting "/" only,
because the "-.mount" SYSTEMD UNIT doesn't depend on "systemd-
fsck@.service" unit, it depends only on "systemd-fsck-root.service", non
existent in TRUSTY's SYSTEMD version. Probably this made SYSTEMD to act
like no error existed.

For SYSTEMD mount units to work, it is needed that no fsck unit error
exists - like when having /var or any other mounting besides root
filesystem - allowing all SYSTEMD units created by snappy to work.

Comparing default setups for TRUSTY and ZESTY:


## TRUSTY

$ dpkg -L systemd | grep fsck
/lib/systemd/systemd-fsck

$ systemctl list-units --all | grep fsck
systemd-...el-LVVAR.service error  inactive dead
systemd-fsck@dev-disk-by\x2dlabel-LVVAR.service
systemd-...el-TESTE.service error  inactive dead
systemd-fsck@dev-disk-by\x2dlabel-TESTE.service

$ systemctl list-units --all | grep mount
-.mountloaded active   mounted /
teste.mountloaded active   mounted /teste
var.mount  loaded active   mounted /var
umount.target  loaded inactive deadUnmount All Filesystems

## ZESTY

$ dpkg -L systemd | grep fsck
/lib/systemd/system/systemd-fsck-root.service
/lib/systemd/system/systemd-fsck@.service
/lib/systemd/system/systemd-fsckd.service
/lib/systemd/system/systemd-fsckd.socket
/lib/systemd/systemd-fsck
/lib/systemd/systemd-fsckd

$ systemctl list-unit-files | grep fsck
systemd-fsck-root.service   static
systemd-fsck@.service   static
systemd-fsck@dev-disk-by\x2dlabel-TESTE.service static
systemd-fsckd.service   static
systemd-fsckd.socketstatic

$ systemctl list-unit-files | grep mount
-.mount   generated
home-inaddy-work.mountgenerated
mnt.mount static
mountall.service  masked
umountfs.service  masked
umountroot.servicemasked
umount.target static


SYSTEMD in TRUSTY was treated differently for FSCK. TRUSTY's version
contains systemd-fsck but not systemd-fsckd, the daemon responsible for
consolidating all fsck information for SYSTEMD journal. It is also clear
that TRUSTY did not include any unit file for systemd-fsck@.service,
that might still be considered for the automatically generated mount
unit files.

You can reproduce this by trying to use TRUSTY SYSTEMD mount units:


## TRUSTY

$ mount /teste

$ mount | grep teste
/dev/sdb2 on /teste type ext4 (rw)

$ systemctl status teste.mount
teste.mount - /teste
   Loaded: loaded (/etc/fstab)
   Active: active (mounted) since Wed 2017-09-27 17:27:21 BRT; 10s ago
Where: /teste
 What: /dev/sdb2
  Process: 1754 ExecUnmount=/bin/umount /teste (code=exited, status=0/SUCCESS)

$ systemctl stop teste.mount

$ systemctl status teste.mount
teste.mount - /teste
   Loaded: loaded (/etc/fstab)
   Active: inactive (dead) since Wed 2017-09-27 17:27:33 BRT; 2s ago
Where: /teste
 What: /dev/disk/by-label/TESTE
  Process: 1778 ExecUnmount=/bin/umount /teste (code=exited, status=0/SUCCESS)

$ mount | grep teste

$ systemctl start teste.mount
Failed to issue method call: Unit 
systemd-fsck@dev-disk-by\x2dlabel-TESTE.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-disk-by\x2dlabel-TESTE.service' for details.


Also, in TRUSTY, SYSTEMD creates the mount units based on /etc/fstab
entries, just like the recent SYSTEMD does, but on them THERE IS NO
setting for fsck dependencies (Requires/After), and, still, it appears
to be considering those fsck dependencies when you try to mount a
".mount" unit, based on errors I showed above for "systemctl start
XXX.mount".


## TRUSTY

$ cat var.mount

# Automatically generated by systemd-fstab-generator

[Unit]
SourcePath=/etc/fstab
DefaultDependencies=no
After=local-fs-pre.target
Conflicts=umount.target
Before=umount.target
Before=local-fs.target

[Mount]
What=/dev/disk/by-label/LVVAR
Where=/var
Type=ext4
FsckPassNo=1

## ZESTY

$ systemctl edit --full mnt.mount
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=local-fs.target