[Bug 1576341] Re: systemd in degraded state on startup in LXD containers
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
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
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
** 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
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
Re: [Bug 1576341] Re: systemd in degraded state on startup in LXD containers
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
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
