Problem still exists in Ubuntu 16.10.
** Summary changed:
- starting any container with umask 007 breaks lxc-stop and prevents host
system shutdown
+ starting any container with umask 007 breaks host system shutdown. lxc-stop
just hangs.
--
You received this bug notification because you are
I reproduced it with the latest mainline kernel as well:
Linux xenialbox 4.9.0-040900rc6-generic #201611201731 SMP Sun Nov 20
22:33:21 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Here's the slightly different syslog output:
Nov 22 14:36:55 xenialbox kernel: [ 484.506570] INFO: task systemd:3086
Linux xenialbox 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642767
Title:
starting any container with
This sounds like a kernel bug to me. Can you please provide the output
of:
uname -a
and try to reproduce this on a newer kernel version and report back?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- If I run lxc-start with umask 007 (or any other value that masks the
- world-execute bit), my host system enters a state with the following
- problems:
+ If I have umask 007 (or any other value that masks the world-execute
+ bit) when I run lxc-start for the first time
** Description changed:
If I run lxc-start with umask 007 (or any other value that masks the
world-execute bit), my host system enters a state with the following
problems:
* lxc-stop hangs forever instead of stopping any container, even one that
wasn't started with umask 007.
*
** Description changed:
If I run lxc-start with umask 007 (or any other value that masks the
world-execute bit), my host system enters a state with the following
problems:
* lxc-stop hangs forever instead of stopping any container, even one that
wasn't started with umask 007.
*
Possibly related: when the problem is triggered, I notice that my guest
instances start with no /etc/resolv.conf and no inet address.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642767
Title:
