** Changed in: lxcfs (Ubuntu Wily)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527666
Title:
lxc on Wily cannot dist-upgrade Xenial
To manage notifications
Let me rephrase - I can't reproduce by hand, even doing apt-get install
--reinstall systemd. adt-run does indeed fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527666
Title:
lxc on Wily
Failing to reproduce this.
I do notice that now systemd is also placing itself into init.scope for
devices cgroup, which i don't think it did before, but that should be
fine (and isn't causing issues here).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: lxcfs (Ubuntu)
Importance: Undecided => High
** Changed in: lxcfs (Ubuntu Wily)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527666
Title:
lxc
On Mon, Dec 21, 2015 at 07:38:29PM -, Serge Hallyn wrote:
> Let me rephrase - I can't reproduce by hand, even doing apt-get install
> --reinstall systemd. adt-run does indeed fail.
I couldn't reproduce that either in the end. Sorry if the report is
contradictory, I made assumptions and then
I've tried downgrading systemd and re-installing, but that did not
suffice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527666
Title:
lxc on Wily cannot dist-upgrade Xenial
To manage
Correction. Rather than systemd being upgraded, I think there's
something that fires a trigger in it that sets off the failure.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1527666
Correction. Rather than systemd being upgraded, I think there's
something that fires a trigger in it that sets off the failure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527666
Title:
lxc on
Sounds like a lxcfs or cgmanager issue, moving to lxcfs for now.
** Package changed: lxc (Ubuntu) => lxcfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1527666
Title:
lxc
Sounds like a lxcfs or cgmanager issue, moving to lxcfs for now.
** Package changed: lxc (Ubuntu) => lxcfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527666
Title:
lxc on Wily cannot
> something that fires a trigger in it that sets off the failure.
The trigger is most likely stuck in "systemctl daemon-reload", which
likely exercises some cgroup reconfiguration. In lxc these are being
redirected to lxcfs/cgmanager.
--
You received this bug notification because you are a
> something that fires a trigger in it that sets off the failure.
The trigger is most likely stuck in "systemctl daemon-reload", which
likely exercises some cgroup reconfiguration. In lxc these are being
redirected to lxcfs/cgmanager.
--
You received this bug notification because you are a
I have this on the armhf production autopkgtest machines, but I wasn't
aware that it is a general problem. These still run an ancient kernel
(3.13) under wily userspace. But it seems it happens under a full wily
amd64 too then.
For me I bisected it to downgrading lxcfs. 0.10-0ubuntu2 works,
I have this on the armhf production autopkgtest machines, but I wasn't
aware that it is a general problem. These still run an ancient kernel
(3.13) under wily userspace. But it seems it happens under a full wily
amd64 too then.
For me I bisected it to downgrading lxcfs. 0.10-0ubuntu2 works,
14 matches
Mail list logo
