[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Mathew Hodson]

systemd SRU to ignore failures to set Nice priority on services in
containers for Xenial in bug 1709536.

** No longer affects: systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Mathew Hodson]

I assume the failures in comment #37 for nfs-common were also caused by
systemd failing to set the Nice priority.

** No longer affects: nfs-utils (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

With a fully updated daily image (lxc launch ubuntu-daily:artful; lxc
exec  apt update; lxc exec  apt full-upgrade; lxc
exec  reboot; lxc exec  systemctl status):

State: running
 Jobs: 0 queued
   Failed: 0 units

Nice work everyone!

Now, ideally, any package that shows up in the container image by
default is checked that this doesn't regress going forward :)

** Changed in: lvm2 (Ubuntu)
 Assignee: Nish Aravamudan (nacc) => (unassigned)

** Changed in: open-iscsi (Ubuntu)
 Assignee: Nish Aravamudan (nacc) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

With a fully updated daily image (lxc launch ubuntu-daily:artful; lxc
exec  apt update; lxc exec  apt full-upgrade; lxc
exec  reboot; lxc exec  systemctl status):

State: running
 Jobs: 0 queued
   Failed: 0 units

Nice work everyone!

Now, ideally, any package that shows up in the container image by
default is checked that this doesn't regress going forward :)

** Changed in: lvm2 (Ubuntu)
 Assignee: Nish Aravamudan (nacc) => (unassigned)

** Changed in: open-iscsi (Ubuntu)
 Assignee: Nish Aravamudan (nacc) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Mathew Hodson]

This bug was fixed in the systemd with 234-2ubuntu6 - Ignore failures to
set Nice priority on services in containers.

---
systemd (234-2ubuntu2) artful; urgency=medium

  * Ignore failures to set Nice priority on services in containers.
  * Disable execute test on armhf.
  * units: set ConditionVirtualization=!private-users on journald audit socket.
It fails to start in unprivileged containers.
  * boot-smoke: refactor ADT test.
Wait for system to settle down and get to either running or degraded state,
then collect all metrics, and exit with an error if any of the tests failed.

 -- Dimitri John Ledkov   Wed, 02 Aug 2017 03:02:03
+0100

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Mathew Hodson]

open-iscsi (2.0.874-4ubuntu1) artful; urgency=medium

  * Merge with Debian unstable. Remaining changes:
- debian/tests: Add Ubuntu autopkgtests.
- debian/iscsi-network-interface.rules, debian/net-interface-handler,
  debian/open-iscsi.install:
  Prevent network interface that contains iscsi root from bouncing
  during boot or going down during shutdown.
  Integrates with resolvconf and initramfs code that writes
  /run/initramfs/open-iscsi.interface
- debian/open-iscsi.maintscript: clean up the obsolete
  iscsi-network-interface upstart job, file on upgrade.
- Let iscsid systemd job run in privileged containers but not in
  unprivileged ones
- Start open-iscsi systemd job when either /etc/iscsi/nodes or
  /sys/class/iscsi_session have content
  Based on patch by Nish Aravamudan, thanks! (LP #1576341)
- add IPv6 support
  + add support for IPV6{DOMAINSEARCH,DNS0,DNS1} to net-interface-handler
LP #1621507
  + Source /run/net6-*.conf when needed.
  + debian/extra/initramfs.local-top: handle IPv6 configs being
shipped in DEVICE6 or /run/net6-*.conf in the initramfs, so we
can fill in /run/initramfs/open-iscsi.interface (LP #1621507)
  * Drop:
- d/extra/initramfs.local-top: When booting from iBFT,
  set the PROTO= entry in /run/net-*.conf accordingly,
  so that other tools, such as cloud-init, can use that
  information. (cloud-init fails if the current PROTO=none
  is used.) (LP: #1684039) (Closes: #866213)
  [ Fixed in Debian 2.0.874-4 ]
  * d/t/test-open-iscsi.py: drop test_daemon test
- With the updates to the systemd units, the services do not run
  unless iSCSI is configured.

 -- Nishanth Aravamudan   Tue, 08 Aug
2017 16:16:27 -0700

** Changed in: open-iscsi (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 234-2ubuntu6

---
systemd (234-2ubuntu6) artful; urgency=medium

  * Disable KillUserProcesses, yet again, with meson this time.
  * Re-enable reboot tests.

 -- Dimitri John Ledkov   Thu, 17 Aug 2017 15:22:35
+0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Mathew Hodson]

** No longer affects: snapd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Dimitri John Ledkov]

snapd is invalid, and will be fixed with
https://github.com/systemd/systemd/pull/6503/files

basically systemd did not ignore failure to set Nice on the service in a
container.

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

** Changed in: snapd (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Mathew Hodson]

** No longer affects: lxd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Christian Reis]

And added a snapd task based on Nish's last comment.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Christian Reis]

I've also noticed that nfs-common triggers a failure:

root@sendmail:~# systemctl --failed
  UNIT   LOAD   ACTIVE SUBDESCRIPTION
● run-rpc_pipefs.mount   loaded failed failed RPC Pipe File System
● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File 
Systems
● lvm2-lvmetad.socketloaded failed failed LVM2 metadata daemon socket

So I've added a task for nfs-common. The remaining failures I believe
have been handled by this bug and are just unfixed in Xenial (and will
likely remain unfixed right?)

** Also affects: nfs-utils (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: snapd (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

In Artful, we have (running with -proposed for open-iscsi and lvm2):

● snapd.service loaded failed failed Snappy daemon 
● snapd.socket  loaded failed failed Socket activation for snapp
● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

snapd team probably need to fix the first two.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

In Artful, we have (running with -proposed for open-iscsi and lvm2):

● snapd.service loaded failed failed Snappy daemon 
● snapd.socket  loaded failed failed Socket activation for snapp
● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

snapd team probably need to fix the first two.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 233-6ubuntu2

---
systemd (233-6ubuntu2) artful; urgency=medium

  [ Michael Biebl ]
  * basic/journal-importer: Fix unaligned access in get_data_size()
(Closes: #862062)

  [ Dimitri John Ledkov ]
  * ubuntu: disable dnssec on any ubuntu releases (LP: #1690605)
  * Cherrypick upstream patch for vio predictable interface names.
  * Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)

  [ Balint Reczey ]
  * Skip starting systemd-remount-fs.service in containers
even when /etc/fstab is present.
This allows entering fully running state even when /etc/fstab
lists / to be mounted from a device which is not present in the
container. (LP: #1576341)

 -- Dimitri John Ledkov   Wed, 17 May 2017 19:24:03
+0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Dimitri John Ledkov]

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

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

** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.05

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

lvm2 fix is in 2.02.168-2ubuntu1 in artful.

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

** Changed in: open-iscsi (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

lvm2 fix is in 2.02.168-2ubuntu1 in artful.

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

** Changed in: open-iscsi (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

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

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Balint Reczey]

Regarding the systemd patch there can be configurations where systemd-
remount-fs is needed and does useful work. In those configurations the
.service file can be overridden by a local one to start.

One other - not too clean - option is locally diverting /lib/systemd
/systemd-remount-fs in image generation to check "mount -f /" before
actually doing the remount and reporting success when  "mount -f /"
fails.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Balint Reczey]

Adding patch for systemd to skip starting systemd-remount-fs.service in
containers.

This is the last piece of the puzzle to see systemd in running state in
an Artful container, comments are welcome! :-)

** Patch added: 
"0001-Skip-starting-systemd-remount-fs.service-in-containe.patch"
   
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1576341/+attachment/4873711/+files/0001-Skip-starting-systemd-remount-fs.service-in-containe.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

I'm going to upload rbalint's fixes in the merges for open-iscsi and
lvm2 I plan on doing this week.

** Changed in: open-iscsi (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: open-iscsi (Ubuntu)
   Status: Triaged => In Progress

** Changed in: open-iscsi (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

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

** Changed in: lvm2 (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

I'm going to upload rbalint's fixes in the merges for open-iscsi and
lvm2 I plan on doing this week.

** Changed in: open-iscsi (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: open-iscsi (Ubuntu)
   Status: Triaged => In Progress

** Changed in: open-iscsi (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

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

** Changed in: lvm2 (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

On 08.05.2017 [11:25:03 -], Balint Reczey wrote:
> >> 1.b i'd like another way to do that, but not sure what a better way would
> >> be.
> > 
> > Yeah, I spent some time looking at the CPC generater and it seems like
> > this is pretty hard-coded:
> > 
> > 999-cpc-fixes.chroot:
> > ## --
> > # for maverick and newer, use LABEL= for the '/' entry in fstab
> > if [ -n "${root_fs_label}" ]; then
> >bl="[:blank:]"
> >lstr="LABEL=${root_fs_label}"
> >sed -i "s,^[^#${bl}]*\([${bl}]*/[${bl}].*\),${lstr}\1," 
> > "${rootd}/etc/fstab"
> > fi
> > cat > /etc/fstab << EOM
> > LABEL=cloudimg-rootfs / ext4 defaults 0 0
> > EOM
> 
> I think the cleanest solution would be providing images for containers
> without this invalid fstab entry.

I *think* containers and VMs use the same cloud image, so I don't think
bifurcating for this one change is reasonable.

> The second cleanest seems to be not starting
> systemd-remount-fs.service in containers, or at least not in lxc.

Except it's possible that a user might have other entries that should be
remounted, possibly? When, say, passing real disks into the container?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

On 08.05.2017 [11:25:03 -], Balint Reczey wrote:
> >> 1.b i'd like another way to do that, but not sure what a better way would
> >> be.
> > 
> > Yeah, I spent some time looking at the CPC generater and it seems like
> > this is pretty hard-coded:
> > 
> > 999-cpc-fixes.chroot:
> > ## --
> > # for maverick and newer, use LABEL= for the '/' entry in fstab
> > if [ -n "${root_fs_label}" ]; then
> >bl="[:blank:]"
> >lstr="LABEL=${root_fs_label}"
> >sed -i "s,^[^#${bl}]*\([${bl}]*/[${bl}].*\),${lstr}\1," 
> > "${rootd}/etc/fstab"
> > fi
> > cat > /etc/fstab << EOM
> > LABEL=cloudimg-rootfs / ext4 defaults 0 0
> > EOM
> 
> I think the cleanest solution would be providing images for containers
> without this invalid fstab entry.

I *think* containers and VMs use the same cloud image, so I don't think
bifurcating for this one change is reasonable.

> The second cleanest seems to be not starting
> systemd-remount-fs.service in containers, or at least not in lxc.

Except it's possible that a user might have other entries that should be
remounted, possibly? When, say, passing real disks into the container?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Balint Reczey]

>> 1.b i'd like another way to do that, but not sure what a better way would
>> be.
> 
> Yeah, I spent some time looking at the CPC generater and it seems like
> this is pretty hard-coded:
> 
> 999-cpc-fixes.chroot:
> ## --
> # for maverick and newer, use LABEL= for the '/' entry in fstab
> if [ -n "${root_fs_label}" ]; then
>bl="[:blank:]"
>lstr="LABEL=${root_fs_label}"
>sed -i "s,^[^#${bl}]*\([${bl}]*/[${bl}].*\),${lstr}\1," 
> "${rootd}/etc/fstab"
> fi
> cat > /etc/fstab << EOM
> LABEL=cloudimg-rootfs / ext4 defaults 0 0
> EOM

I think the cleanest solution would be providing images for containers without 
this invalid fstab entry.
The second cleanest seems to be not starting systemd-remount-fs.service in 
containers, or at least not in lxc.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Balint Reczey]

Fixed the format of the open-iscsi conditions, it works nicely in
(privileged and not privileged) artful containers.


** Patch added: "open-iscsi_2.0.873+git0.3b4b4500-14ubuntu18.patch"
   
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1576341/+attachment/4873428/+files/open-iscsi_2.0.873+git0.3b4b4500-14ubuntu18.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Ubuntu Foundations Team Bug Bot]

The attachment "lvm2_2.02.167-1ubuntu7.patch" 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Balint Reczey]

Patch for lvm2, tested in zesty lxc container and VM (for regressions).


** Patch added: "lvm2_2.02.167-1ubuntu7.patch"
   
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1576341/+attachment/4873198/+files/lvm2_2.02.167-1ubuntu7.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Balint Reczey]

>> 1.c does lvm also fail in privileged containers?  I can see no use to
>> running it (for now) in an unprivileged container, so the same solution
>> as 1.a seems reasonable.
>
> It also fails in privileged containers in the same way (see 2.b in
> comment 20). Note that it works if I manually start the socket after
> boot.

It seems /lib/systemd/system/lvm2-monitor.service also needs the
"ConditionVirtualization=!container" line.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

On 29.03.2017 [03:19:16 -], Serge Hallyn wrote:
> Thanks, Nish.  My thoughts:
> 
> 1.a sounds good

Ack.
 
> 1.b i'd like another way to do that, but not sure what a better way would
> be.

Yeah, I spent some time looking at the CPC generater and it seems like
this is pretty hard-coded:

999-cpc-fixes.chroot:
## --
# for maverick and newer, use LABEL= for the '/' entry in fstab
if [ -n "${root_fs_label}" ]; then
   bl="[:blank:]"
   lstr="LABEL=${root_fs_label}"
   sed -i "s,^[^#${bl}]*\([${bl}]*/[${bl}].*\),${lstr}\1," "${rootd}/etc/fstab"
fi
cat > /etc/fstab << EOM
LABEL=cloudimg-rootfs   /   ext4 defaults 0 0
EOM

> 1.c does lvm also fail in privileged containers?  I can see no use to
> running it (for now) in an unprivileged container, so the same solution
> as 1.a seems reasonable.

It also fails in privileged containers in the same way (see 2.b in
comment 20). Note that it works if I manually start the socket after
boot.

> 1.d
> CAP_ADMIN_READ is not a real capability.  So if 1.d is fixed by that,
> then something else is wrong.

Right, follow-on comments indicated it was a thinko on my part. I think
it make sense, based upon the context in the audit bug that perhaps we
just don't do auditing in unprivileged containers (similar to the 1.a
change)?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

On 29.03.2017 [03:19:16 -], Serge Hallyn wrote:
> Thanks, Nish.  My thoughts:
> 
> 1.a sounds good

Ack.
 
> 1.b i'd like another way to do that, but not sure what a better way would
> be.

Yeah, I spent some time looking at the CPC generater and it seems like
this is pretty hard-coded:

999-cpc-fixes.chroot:
## --
# for maverick and newer, use LABEL= for the '/' entry in fstab
if [ -n "${root_fs_label}" ]; then
   bl="[:blank:]"
   lstr="LABEL=${root_fs_label}"
   sed -i "s,^[^#${bl}]*\([${bl}]*/[${bl}].*\),${lstr}\1," "${rootd}/etc/fstab"
fi
cat > /etc/fstab << EOM
LABEL=cloudimg-rootfs   /   ext4 defaults 0 0
EOM

> 1.c does lvm also fail in privileged containers?  I can see no use to
> running it (for now) in an unprivileged container, so the same solution
> as 1.a seems reasonable.

It also fails in privileged containers in the same way (see 2.b in
comment 20). Note that it works if I manually start the socket after
boot.

> 1.d
> CAP_ADMIN_READ is not a real capability.  So if 1.d is fixed by that,
> then something else is wrong.

Right, follow-on comments indicated it was a thinko on my part. I think
it make sense, based upon the context in the audit bug that perhaps we
just don't do auditing in unprivileged containers (similar to the 1.a
change)?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Serge Hallyn]

Thanks, Nish.  My thoughts:

1.a sounds good

1.b i'd like another way to do that, but not sure what a better way would
be.

1.c does lvm also fail in privileged containers?  I can see no use to
running it (for now) in an unprivileged container, so the same solution
as 1.a seems reasonable.

1.d
CAP_ADMIN_READ is not a real capability.  So if 1.d is fixed by that,
then something else is wrong.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

Ok, the audit stuff was 'resolved' in LP: #1457054, where I think
everyone decided to agree that unprivileged containers didn't matter...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

heh, after a few more sips of coffee and actually reading the manpage,
my 1.d.1 is obviously incorrect because CAP_ADMIN_READ is not a
capability. So in effect it's masking out the audit socket :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

Wanted to level-set (and subscribing pitti and hallyn for their advice):

1) LXD unprivileged containers:

4 services in the Zesty daily are failed at start:

1.a) iscsid.service

  This is because iscsid needs CAP_IPC_LOCK to run mlockall().
Unprivileged containers end up failing in the host kernel.

  I believe the right way about this is to make the change hallyn did to
open-iscsi.service in iscsid.service and make open-iscsi.service
properly depend on iscsid.service. But I also think the change made by
hallyn is too broad and means even privileged containers cannot use
iscsi, which does not seem to be strictly true.

1.a.1) Proposed solution: http://paste.ubuntu.com/24196051/

  Effectively, only run iscsid if not in a user namespace (which is
where the capabilities get dropped, aiui). And open-iscsi service adds
conditions (adapter from Fedora's service file) to check that nodes are
defined (which would imply some configuration has been done) and a
session exists (which I think means that /etc/iscsi/iscsid.conf contains
node.startup=automatic and iscsid has started up a session therefore).

  If we are worried about the potential breakage (I need to of course
test all this in the various iSCSI configurations), we might consider
just making the first change (ConditionVirtualization=!private-users) to
both .service files, but I feel like that is mostly a workaround for not
being able to express cleanly the dependency between the two services:
open-iscsi.service can only run if iscsid.service is running; but if
iscsid.service is not running because of a Condition, then open-
iscsi.service should not be in a failed state.

1.b) systemd-remount-fs.service

  z2 systemd-remount-fs[50]: mount: can't find LABEL=cloudimg-rootfs

  /etc/fstab:
LABEL=cloudimg-rootfs   /ext4   defaults0 0

  This doesn't really make sense in the context of LXD containers
afaict, because they don't have a /dev/disk/by-label necessarily? Also,
the / is all configured by LXD in practice, not by how the cloud-image
is configured?

1.b.1) Proposed solution, comment out the entry in /etc/fstab in the LXD
images.

1.c) lvm2-lvmetad.socket

  lvm[61]:   Daemon lvmetad returned error 104
  lvm[61]:   WARNING: Failed to connect to lvmetad. Falling back to device 
scanning.
  ...
  lvm2-lvmetad.socket: Trigger limit hit, refusing further activation.

  But manually running `systemctl start lvm2-lvmetad.socket` at `lxc
exec z1 bash`, works. That seems confusing and implies some sort of
ordering issue? (Note that confusingly `systemctl restart
lvm2-lvmetad.socket` does *not* work.)

1.c.1) I don't have a proposed solution for this.

1.d) systemd-journal-audit.socket

  I found this older thread: https://lists.freedesktop.org/archives
/systemd-devel/2015-May/032113.html on this topic. Specifically,
https://lists.freedesktop.org/archives/systemd-
devel/2015-May/032126.html.

  Looking at the socket file, though, I see:

  ConditionCapability=CAP_AUDIT_READ

  which I do not believe is the same as CAP_ADMIN_READ. I don't know if
the ML post or the change are incorrect, but I did verify that using
CAP_ADMIN_READ in the container instead of CAP_AUDIT_READ did correctly
conditionalize the socket start, while CAP_AUDIT_READ does not.

1.d.1) Proposed solution: changing the ConditionCapability to
CAP_ADMIN_READ.

2) Privileged containers

2.a) systemd-remount-fs.service

  Same as 1.b) above.

2.b) lvm2-lvmetad.socket

  Same as 1.c) above.

With the changes in 1.a.1, 1.b.1 and 1.d.1:

3) Unpriviled container

3.a) Only 1.c) remains, and after issuing `systemctl start
lvm2-lvmetad.socket`, `systemctl status` reports 'running'.

4) Privileged container

4.a) same as 3.a)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

** Summary changed:

- fails in lxd container
+ systemd in degraded state on startup in LXD containers

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341

Title:
  systemd in degraded state on startup in LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs