I'm going off some more testing with that in mind what I documented on the bug already.
I really want to understand why it hits you now and if this is a SRU- regression, so here some questions. Questions to Logan: - Could you share your guest XML to help me to understand what combination drives your guest into being stopped by this apparmor DENY now? - Did the workaround suggested by Jamie fix it for you? - Could you also try downgrading to 1.3.1-1ubuntu10.7 if that get you working again? - I have made assumptions, but want to confirm what are the releases you are using for Ubuntu, Cloud-Archive, Openstack? Questions to the Cloud Archive Team: - It didn't in mine, but did that show up in any of your usual regular tests? - is the referred Openstack commit active in any of our cloud-archive release (if so in which)? - Can we reproduce that somehow to iterate more quickly on it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665698 Title: /etc/qemu-ifup not allowed by apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1665698/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
