Hello Scott, or anyone else affected, Accepted curtin into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr399-0ubuntu1~16.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: curtin (Ubuntu) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu) Status: New => Fix Released ** Changed in: curtin (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1592149 Title: simple networking mode (net-meta) does not account for device names Status in curtin: Fix Committed Status in curtin package in Ubuntu: Fix Released Status in curtin source package in Xenial: Fix Committed Bug description: [Impact] * Users which do not use a customized network configuration rely on curtin's fallback/automatic configuration. On Xenial and newer systems the network configuration that is generated doesn't always work due to the persistent nic names which do not match between initial install environment and booting the system after installation. This affects all curtin releases which use auto configure networking and an Ubuntu release which uses persistent network device nameing. * This SRU resolves the bug by ensuring auto configured networking includes nic naming rules to ensure the network device names match what is generated in the config. [Test Case] * On a Xenial 16.04 system - % apt-get install curtin - % OUTPUT_NETWORK_CONFIG=rendered-eni curtin net-meta -t /tmp auto FAIL: Systems with the error will print an interfaces file to stdout PASS: Systems with the fix with emit host networking config to the file "rendered-eni" and produces no output to stdout. [Regression Potential] * Users that use auto configuration may find that the persistent nic names in the target system are no longer ethN, but named based on location. [Original Description] 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'll attach logs just for completeness. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1592149/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : [email protected] Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
