[Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition
Rafael David Tinoco
rafael.tinoco at canonical.com
Fri Sep 29 18:17:45 UTC 2017
Okay, so another quick workaround, now keeping the fsck enabled for the
volumes:
Create a file called "/lib/systemd/upstart/systemd-fsck at .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 at .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 at .service /lib/systemd/upstart/multi-user.target.wants/systemd-fsck at .service
$ sudo systemctl daemon-reload
This will allow the mount units to work using systemd in Trusty:
inaddy at trustylivepatch:~$ sudo systemctl start teste.mount
inaddy at trustylivepatch:~$ df -kh | grep teste
/dev/sdb2 976M 1.3M 908M 1% /teste
inaddy at trustylivepatch:~$ sudo systemctl stop teste.mount
inaddy at 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
Foundations Bugs, 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 at 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 at dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck at dev-mapper-vg00\x2dvarvol.service' for details.
)
The error with /var isolated but without using LVM:
root at 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 at 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 at 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 at 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 at dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck at 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 at 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 at 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 at ubuntu:~# apt update
root at ubuntu:~# apt upgrade -y
root at ubuntu:~# apt install -y snapd
root at ubuntu:~# reboot
# After reboot, check kernel version and try to install the canonical-livepatch snap:
root at 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 at ubuntu:~# snap list
No snaps are installed yet. Try "snap install hello-world".
root at 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 at dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck at dev-mapper-vg00\x2dvarvol.service' for details.
)
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1718966/+subscriptions
More information about the foundations-bugs
mailing list