The bug is STILL present and breaks libvirt-bin upon upgrade from 14.04
to 16.04
Performing the steps from comment 34 worked around the breakage.
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386465/comments/34
** Changed in: libvirt (Ubuntu)
Status: Expired => Confirmed
**
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Thanks @mahmoh,
that's interesting. Perhaps we should add a comment in the shipped
/etc/default/libvirt-bin?
Why had you added the -l? Is there a published recipe you were
following, and should that be updated?
** Changed in: libvirt (Ubuntu)
Status: Expired => Confirmed
--
You
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
I upgraded from 14.04 to 14.10 installed libvirt and got the same error:
From syslog I have pre aa-audit and then with aa-audit it seems to aa-
audit clears the bug with audit removed it continues to work.
Post audit log:
Apr 14 20:19:50 dnshost11 kernel: [ 1284.666816] audit_printk_skb: 36
Thanks - as you have no more issues i'll mark the bug 'invalid' meaning
cannot currently be reproduced. If it happens again please re-open the
bug.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
I can reproduce this bug
** Changed in: libvirt (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents
Thanks you for the information - that's quite frustrating. It seems quite
clear (between this bug and some others) that there is a hard-to-trigger
bug in the libvirt apparmor policy, but I've not yet spotted any obvious
trigger.
I'm marking this bug invalid meaning cannot be reproduced, but if
