Yes. Thanks, Jamie.
Kapil,. can you re-try your experiment and see if everything now works?
I"ll optimistically mark the bug Fix Released. Please re-open if
rsyslog still does not start, or open a new bug if you find new barriers
to using the cloud template.
** Changed in: lxc (Ubuntu)
Should this bug be updated now that the upstart part of 978297 is fixed?
--
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/978147
Title:
rsyslogd fails to start in cloud template
To manag
Upstart and apparmor should be updated, not rsyslog. See bug #978297.
** Changed in: rsyslog (Ubuntu)
Status: New => Won't Fix
--
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/978147
It seems rsyslog's policy is by default disabled.
The actual bug is because apparmor-profile-load isn't allowed to read
/sys/module/apparmor/parameters/enabled, and then returns failure.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Also affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
--
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/978147
Title:
rsyslogd fails to start in cloud template
To
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?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which i
