rsyslogd fails to start in cloud template
Bug #978147 reported by
Kapil Thangavelu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
rsyslog (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Attempting to use the cloud-init functionality of the new 'ubuntu-cloud' template fails due to a rsyslog not starting.
Looking at the rsyslog upstart job, it appears that the app armor profile here is causing the issue. Part of this is might be due to the lack of containerization around syslog call as noted by hallyn.
Commenting out rsyslogd app armor usage, allows it to start, and cloud-init proceeds.
Changed in lxc (Ubuntu): | |
importance: | Undecided → High |
status: | New → Confirmed |
To post a comment you must log in.
The problem is that rsyslog does
/lib/init/ apparmor- profile- load usr.sbin.rsyslogd
in pre-start and isn't allowed to.
What's the best thing to do? not do that in a container? Ignore -EPERM failures?