container startup must not fail if setup_kmsg fails
Bug #1097312 reported by
Serge Hallyn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Medium
|
Unassigned |
Bug Description
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.
=======
description: | updated |
Changed in lxc (Ubuntu Quantal): | |
status: | Triaged → In Progress |
To post a comment you must log in.
(medium priority because this does not affect most regular lxc usage)