Comment 22 for bug 1597644

FYI setting dynamic_ownership=0 is really a bad idea and liable to break nova in suprising ways. This console.log problem is one example, but I'm confident this will have broken other parts of Nova - quite possibly save/restore to file. I'm guessing the reason this is done to was to prevent libvirt trying to change ownership for the quobyte disk images, presumably because the server is configured to deny ownership changes.

If so, a much better approach is to enhance nova so that it can set a <seclabel> element against *just* the quobyte backed disks, that tells libvirt to skip ownership changes for those disks. That way operation of libvirt / QEMU in general will not be affect, thus avoiding nasty side-effects such as this console.log problem.

IMHO we should explicitly consider dynamic_ownership=0 to be an unsupported config for libvirt with Nova.