** Description changed:
setup_kmsg is a convenience to have container syslog messages (generated
by userspace) directed at the console. However it fails the container
must not fail to start.
+
+ ========================
+ SRU Justification
+ Impact: certain containers will fail to start
+ Development fix: if /dev/kmsg could not be set up, don't fail container
startup
+ Stable fix: same as development fix
+ Test case:
+ sudo lxc-create -t sshd -n ssh1
+ sudo lxc-start -n ssh1
+ Regression potential: containers can run fine without setup_kmsg() having
run, so allowing container startup to proceed when setup_kmsg() fails should
introduce no regression.
+ ========================
** Changed in: lxc (Ubuntu Quantal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097312
Title:
container startup must not fail if setup_kmsg fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1097312/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
