Comment 21 for bug 1583009

Thanks Saverio for your ping on this.
I wonder why I haven't seen this yet out of a openstack context, might be just the scale of it but I still wonder. I run all sort of libvirt/qemu upgrade tests on a regular cadence and among others this includes Trusty->Xenial and so far none hit this issue - all guests where fine afterwards and libvirt reachable.
This might be just some sort of race or even special config, but since Mikhail in comment #19 reported to see this on some of more equally configured systems the latter is unlikely.

Since recently in weird "something failed" issues around libvirt there was apparmor involved I wonder if one of you had uncommon apparmor reports in dmesg. There are always a few depending on features you use, but if you could attach the log here we could parse through if there is an unusual one.

Bumping the prio on the Cloud Archive Task if they have seen that or reports of it.