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:
** 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:
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
## 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
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
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).
** 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
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
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
** 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
** 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
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
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
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
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
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
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
-
** 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
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.
** 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
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
21 matches
Mail list logo