Hello Jorge, 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 ** Tags added: verification-needed ** Also affects: curtin (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu) Status: New => Fix Released ** Changed in: curtin (Ubuntu Xenial) Status: New => Incomplete ** Changed in: curtin (Ubuntu Xenial) Status: Incomplete => Fix Committed -- 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/1588547 Title: Generated bonding configuration is incorrect. Status in curtin: Fix Committed Status in MAAS: Opinion Status in curtin package in Ubuntu: Fix Released Status in curtin source package in Xenial: Fix Committed Bug description: [Impact] * Users attempting to configure nic bonding and using both ipv4 and ipv6 encounter a misconfigured network due to a bug in curtin's handling of bond configuration and ipv6. The error results in superflous attributes and then broken ipv4 entries if preceeded by an ipv6 address. This affects all curtin releases which support networking configuration. * This SRU fixes bonding and ipv6 configurations by no longer emitting attributes for aliased interfaces and calculating the correct inet type for a given interface. [Test Case] * On a Xenial 16.04 system - apt-get install curtin - cat >test.yaml <<EOF # YAML example of a simple network config network: version: 1 config: # Physical interfaces. - type: physical name: eth0 mac_address: "c0:d6:9f:2c:e8:80" subnets: - type: static address: fde9:8f83:4a81:1:0:1:0:6/64 - type: static address: 192.168.0.1/24 EOF - curtin apply_net -c test.yaml --target target PASS: both greps return zero FAIL: either grep returns non-zero - grep "^iface eth0 inet6 static" target/etc/network/interfaces - grep "^iface eth0:1 inet static" target/etc/network/interfaces [Regression Potential] * Low; users of this configuration would be broken already [Original Description] [Environment] MAAS 2.0 [Description] Given the following configuration: http://img.ctrlv.in/img/16/06/02/5750ac35c78f8.png The resulting /etc/network/interfaces looks as following: http://paste.ubuntu.com/16931445/ Some bad aspects of the resulting configuration are: 1) An ipv4 address is configured on the alias, while an ipv6 address was expected, auto bond0:1 iface bond0:1 inet6 static address 172.27.72.7/26 2) It seems that there is no need to configure the bond-* options on the alias interfaces as these options are inherited. 3) Could be possible to describe why and how the hwaddresses are selected for the aliases? To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1588547/+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
