I thought this might after all be an effect of running from git causing some trouble. But then I found [1] which changed at least code that is related. But that would be the "ID-name" portion. That is fine - the fail to get the id really is the debug setup.
What is interesting is the drop of the double minus. qemuDomainSetPrivatePaths: "%s/domain-%s" With %s being from virDomainObjGetShortName as: "%d-%.*s" So where does the "domain--" come from? Essentially the paths did NOT change but the rules did. And that is in fact an artifact of the test env. The check for the ID returns "-1" for not found. And due to that the "--1" gets rendered. Nice but useless debugging as it is not a real case (but worth to understand), closing the issue :-) [1]: https://libvirt.org/git/?p=libvirt.git;a=commit;h=5102be52d8699a5200f25091de2d25afe3841d6d ** Changed in: libvirt (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718126 Title: newer libvirt changed paths which breaks virt-aa-helper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1718126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
