[Bug 1762769] Re: missing entry at apparmor profile for nova instances

Stefan Hoffmann 1762769 at bugs.launchpad.net
Mon Apr 23 16:12:16 UTC 2018


For the libvirt 1.3.1 setup i have installed:

libvirt-bin       1.3.1-1ubuntu10.21
libvirt0:amd64    1.3.1-1ubuntu10.21
python-libvirt    1.3.1-1ubuntu1.1


To your previous commend:

The qemu arguments for console log and the instance xml looks good.
I can't provide the instance with openstack and start it with virsh, because the virsh instance is deleted after failure (I assume from libvirt or nova)

But I can provide the logfile of libvirt with debug information (this is very much output).
The instance id is 2691027e-9d67-4f78-841f-01e6c809e8fc
I can see, that the apparmor profile is created and there the information about the logfile is shown. But this is only an logentry at the libvirt.log. I don't know, how this informations are given to apparmor or how the profile is created.

I hope this informations helped.

** Attachment added: "libvirt log output debug mode"
   https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1762769/+attachment/5125917/+files/libvirt.log

-- 
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:
  New
Status in libvirt package in Ubuntu:
  Incomplete

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