Thanks Matt for your reply.
AFAIK that is what smb already tried in comment #4.
Never the less I checked the upgrade path once more.
With a modified conffile (just an empty line, but to not get the new one as in
the bug report here)
And with an old guest created on Xenial.
It was not triggering the apparmor denies.
https://launchpadlibrarian.net/288736150/apt.xml also didn't hold a lot
of differences to my guests that would help me to trigger the issue.
That said - I still look out to understand what bit of config triggers that
accesses - as a valid repro is usually recommended for the SRU.
In the worst case, we have luck to have you and Simon being able to verify -
but I usually at least try to be able to reproduce.
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
virt-aa-helper Apparmor profile missing rules for name resolution
To manage notifications about this bug go to:
ubuntu-bugs mailing list