By fixing the symlink-in-path issue we thought of all sub-levels of the file path but one - if the actual file is the symlink. In that case the new code no more resolves it and that is our current bug.
I extended the former test by those of this bug to ensure the fix doesn't break anything we fixed with the recent change. That xml is attached here. With the fix it creates ... "/dev/zd0" rwk, "/dev/dm-0" rwk, "/run/symlinkdisk-doesexist" rwk, "/run/symlinkdisk-doesnotexist" rwk, "/run/symlinksocket-doesexist" rw, "/run/symlinksocket-doesnotexist" rw, "/run/pathdoesnotexist/symlinksocket" rw, "/nothin/atall/exists" rw, "/run/symlinknet-doesexist" rw, "/run/symlinknet-doesnotexist" rw, The first two means the old case is fixed again. The rest shows that the issue we solved before is not showing up again due to the new change. ** Attachment added: "test.xml" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1756394/+attachment/5083800/+files/test.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756394 Title: Upgrading libvirt from 4.0.0-1ubuntu4 to 4.0.0-1ubuntu5 introduced a permission denied on device error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1756394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
