[Bug 1762769] Re: missing entry at apparmor profile for nova instances
ChristianEhrhardt
1762769 at bugs.launchpad.net
Wed May 2 06:58:52 UTC 2018
Interesting, I didn't know about the need of that stdio_handler.
But still the issue is solved then - great.
I'll set the status to invalid then to reflect that (we have no closed).
Thanks Stefan!
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Invalid
** Changed in: cloud-archive
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1762769
Title:
missing entry at apparmor profile for nova instances
Status in Ubuntu Cloud Archive:
Invalid
Status in libvirt package in Ubuntu:
Invalid
Bug description:
My nova instances can't start, because no access to
/var/lib/nova/instances/b952cef8-7a7a-
4d45-a7a9-e4b15b2aae5c/console.log
The apparmor profile is created at /etc/apparmor.d/libvirt/libvirt-
f146b809-e393-48c9-b325-5c2ae6c20e39.files, but at this profile an
enty for console.log is missing
The apparmor profile says: "# DO NOT EDIT THIS FILE DIRECTLY. IT IS
MANAGED BY LIBVIRT." I have no idea, how to configure libvirt, to
expand the profile.
I'm working on
Ubuntu 16.04,
libvirtd (libvirt) 3.6.0
nova 9.1.0
apparmor 2.10.95
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1762769/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list