At least it gets triggered by this change. If I revert this change on current trunk, everything starts working again.
Furthermore, I nailed it down to the test classes that this review touches is indeed the ones that triggers the exception, namely LibvirtConfigGuestInterfaceTest and LibvirtConfigGuestTest.
At least it gets triggered by this change. If I revert this change on current trunk, everything starts working again.
Furthermore, I nailed it down to the test classes that this review touches is indeed the ones that triggers the exception, namely LibvirtConfigGu estInterfaceTes t and LibvirtConfigGu estTest.