** 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 Ledk
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
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 S
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
CA
** No longer affects: lxd (Ubuntu)
--
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/1576341
Title:
systemd in degraded state on startup in LXD containers
Status in lvm2 pac
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:
** No longer affects: snapd (Ubuntu)
--
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/1576341
Title:
systemd in degraded state on startup in LXD containers
Status in lvm2 p
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 (Ub
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 conta
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 ConditionVi
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 containe
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
htt
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.l
** 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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1576341
Title:
system
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 kerne
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
Touch seeded packages, whic
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpa
>> 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 star
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
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
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.
>> 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 fst
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
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:/
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 g
** Changed in: lvm2 (Ubuntu)
Status: In Progress => Fix Committed
--
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/1576341
Title:
systemd in degraded state on startup
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
Touch seeded packages, wh
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 F
And added a snapd task based on Nish's last comment.
--
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/1576341
Title:
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-cp
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:
> > ## -
31 matches
Mail list logo
