I ran
nosetests3 -v tests/vmtests/test_basic.py:XenialTestBasic
and was seeing failures.
That does an install without network config, so it relies on 'net-meta' of 'auto'.
The install worked, but boot failed as networking was not configured.
The issue is that the net-meta was writing /etc/network/interfaces file, but no udev rules or other mechanism to ensure that the device got the same name in the new environment. That, coupled with a change in the commands between 'launch' and 'xkvm' meant that the install environment named the device 'ens3' and the installed environment 'ens4'.
I ran test_basic. py:XenialTestBa sic
nosetests3 -v tests/vmtests/
and was seeing failures.
That does an install without network config, so it relies on 'net-meta' of 'auto'.
The install worked, but boot failed as networking was not configured.
The issue is that the net-meta was writing /etc/network/ interfaces file, but no udev rules or other mechanism to ensure that the device got the same name in the new environment. That, coupled with a change in the commands between 'launch' and 'xkvm' meant that the install environment named the device 'ens3' and the installed environment 'ens4'.
I'll attach logs just for completeness.