Ubuntu server jenkins now runs integration tests with for xenial-proposed.
It's latest run at [1] passed and ran the tests listed below that verify
this bug if fixed.
I've attached 2 files for posterity
curtin-vmtest-proposed-x-22-archive.zip
curtin-vmtest-proposed-x-22-console.log
artifacts of curtin vmtest-proposed-x build 22
You can verify that the installation of curtin used the version shown by:
$ grep -r "Installation started" archive/ | head -n 1
archive/output/ZestyTestNetworkIPV6Vlan/logs/install-serial.log:[ 9.954624] cloud-init[1518]: curtin: Installation started. (0.1.0~bzr470-0ubuntu1~16.04.1)
Ubuntu server jenkins now runs integration tests with for xenial-proposed.
It's latest run at [1] passed and ran the tests listed below that verify
this bug if fixed.
bug 1645515 tests/vmtests/ test_iscsi. py test_nvme. py tests/vmtests/ test_basic. py
bug 1665701 tests/vmtests/
I've attached 2 files for posterity vmtest- proposed- x-22-archive. zip vmtest- proposed- x-22-console. log
curtin-
curtin-
artifacts of curtin vmtest-proposed-x build 22
You can verify that the installation of curtin used the version shown by: output/ ZestyTestNetwor kIPV6Vlan/ logs/install- serial. log:[ 9.954624] cloud-init[1518]: curtin: Installation started. (0.1.0~ bzr470- 0ubuntu1~ 16.04.1)
$ grep -r "Installation started" archive/ | head -n 1
archive/
-- /jenkins. ubuntu. com/server/ view/Curtin/ job/curtin- vmtest- proposed- x/22/
[1] https:/