Comment 3 for bug 1967956

So my initial thought was that this was an apparmor enforcement issue, and that does not appear to be the case. It clearly looks like its a problem with the uid ( I believe 64055 in this case is libvirt-qemu) and gid ( ??? ). However, our data capture does not collect this (grrrr...).

I suspect that this is due to some restrictions of permissions on directories somewhere. Will need to recreate it in order to walk through it and see what this issue is. If there is the possibility of providing the permissions on the directory and fail (as well as the information to confirm the uid/gid - i.e. which uid and gid this is) it would help narrow it down. Until then, a recreate is necessary.