[Yahoo-eng-team] [Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line
This bug was fixed in the package cloud-init - 0.7.8-68-gca3ae67-0ubuntu1~16.10.1 --- cloud-init (0.7.8-68-gca3ae67-0ubuntu1~16.10.1) yakkety; urgency=medium * debian/cherry-pick: add utility for cherry picking commits from upstream into patches in debian/patches. * New upstream snapshot. - mounts: use mount -a again to accomplish mounts (LP: #1647708) - CloudSigma: Fix bug where datasource was not loaded in local search. (LP: #1648380) - when adding a user, strip whitespace from group list [Lars Kellogg-Stedman] (LP: #1354694) - fix decoding of utf-8 chars in yaml test - Replace usage of sys_netdev_info with read_sys_net (LP: #1625766) - fix problems found in python2.6 test. - OpenStack: extend physical types to include hyperv, hw_veb, vhost_user. (LP: #1642679) - tests: fix assumptions that expected no eth0 in system. (LP: #1644043) - net/cmdline: Consider ip= or ip6= on command line not only ip= (LP: #1639930) - Just use file logging by default [Joshua Harlow] (LP: #1643990) - Improve formatting for ProcessExecutionError [Wesley Wiedenmeier] - flake8: fix trailing white space - Doc: various documentation fixes [Sean Bright] - cloudinit/config/cc_rh_subscription.py: Remove repos before adding [Brent Baude] - packages/redhat: fix rpm spec file. - main: set TZ in environment if not already set. [Ryan Harper] - disk_setup: Use sectors as unit when formatting MBR disks with sfdisk. [Daniel Watkins] (LP: #1460715) -- Scott MoserMon, 19 Dec 2016 15:07:12 -0500 ** Changed in: cloud-init (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1639930 Title: initramfs network configuration ignored if only ip6= on kernel command line Status in cloud-init: Fix Released Status in MAAS: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Yakkety: Fix Released Bug description: === Begin SRU Template === [Impact] On a system booted with both ip6= and ip= on the kernel command line cloud-init will raise an exception and fail to process user-data and have its normal affect on boot. That is because cloud-init previously raised an exception when more than one file in /run/net*.conf declared the same DEVICE. Changes to isc-dhcp and initramfs-tools have changed their behavior and cloud-init has to adjust to allow DEVICE6= and DEVICE= in separate files. [Test Case] Boot a system on a network with both ipv4 and ipv6 dhcp servers, and pass kernel command line with: ip=dhcp ip6=dhcp [Regression Potential] Regression seems unlikely as this is relaxing a check. Where previously an exception would have been raised, cloud-init will now go on. So it seems most likely, something that didn't work before (due to raised exception) would now still not work, but with failures. That is not expected, but that would likely be where regressions were found. === End SRU Template === In changes made under bug 1621615 (specifically a1cdebdea), we now expect that there may be a 'ip6=' argument on the kernel command line. The changes made did not test the case where there is 'ip6=' and no 'ip='. The code currently will return with no network configuration found if there is only ip6=... Related bugs: * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1639930/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line
No maas changes were required here, since it always specifies both ip= and ip6= ** Changed in: maas Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1639930 Title: initramfs network configuration ignored if only ip6= on kernel command line Status in cloud-init: Fix Released Status in MAAS: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Yakkety: In Progress Bug description: === Begin SRU Template === [Impact] On a system booted with both ip6= and ip= on the kernel command line cloud-init will raise an exception and fail to process user-data and have its normal affect on boot. That is because cloud-init previously raised an exception when more than one file in /run/net*.conf declared the same DEVICE. Changes to isc-dhcp and initramfs-tools have changed their behavior and cloud-init has to adjust to allow DEVICE6= and DEVICE= in separate files. [Test Case] Boot a system on a network with both ipv4 and ipv6 dhcp servers, and pass kernel command line with: ip=dhcp ip6=dhcp [Regression Potential] Regression seems unlikely as this is relaxing a check. Where previously an exception would have been raised, cloud-init will now go on. So it seems most likely, something that didn't work before (due to raised exception) would now still not work, but with failures. That is not expected, but that would likely be where regressions were found. === End SRU Template === In changes made under bug 1621615 (specifically a1cdebdea), we now expect that there may be a 'ip6=' argument on the kernel command line. The changes made did not test the case where there is 'ip6=' and no 'ip='. The code currently will return with no network configuration found if there is only ip6=... Related bugs: * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1639930/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line
This is fixed in cloud-init 0.7.9. ** Changed in: cloud-init Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1639930 Title: initramfs network configuration ignored if only ip6= on kernel command line Status in cloud-init: Fix Released Status in MAAS: New Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Yakkety: In Progress Bug description: === Begin SRU Template === [Impact] On a system booted with both ip6= and ip= on the kernel command line cloud-init will raise an exception and fail to process user-data and have its normal affect on boot. That is because cloud-init previously raised an exception when more than one file in /run/net*.conf declared the same DEVICE. Changes to isc-dhcp and initramfs-tools have changed their behavior and cloud-init has to adjust to allow DEVICE6= and DEVICE= in separate files. [Test Case] Boot a system on a network with both ipv4 and ipv6 dhcp servers, and pass kernel command line with: ip=dhcp ip6=dhcp [Regression Potential] Regression seems unlikely as this is relaxing a check. Where previously an exception would have been raised, cloud-init will now go on. So it seems most likely, something that didn't work before (due to raised exception) would now still not work, but with failures. That is not expected, but that would likely be where regressions were found. === End SRU Template === In changes made under bug 1621615 (specifically a1cdebdea), we now expect that there may be a 'ip6=' argument on the kernel command line. The changes made did not test the case where there is 'ip6=' and no 'ip='. The code currently will return with no network configuration found if there is only ip6=... Related bugs: * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1639930/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line
This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb- 0ubuntu1~16.04.2 --- cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.2) xenial-proposed; urgency=medium * cherry-pick 18203bf: disk_setup: Use sectors as unit when formatting MBR disks with sfdisk. (LP: #1460715) * cherry-pick 6e92c5f: net/cmdline: Consider ip= or ip6= on command line not only ip= (LP: #1639930) * cherry-pick 8c6878a: tests: fix assumptions that expected no eth0 in system. (LP: #1644043) * cherry-pick 2d2ec70: OpenStack: extend physical types to include hyperv, hw_veb, vhost_user. (LP: #1642679) -- Scott MoserThu, 01 Dec 2016 16:57:39 -0500 ** Changed in: cloud-init (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1639930 Title: initramfs network configuration ignored if only ip6= on kernel command line Status in cloud-init: Fix Committed Status in MAAS: New Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Yakkety: In Progress Bug description: === Begin SRU Template === [Impact] On a system booted with both ip6= and ip= on the kernel command line cloud-init will raise an exception and fail to process user-data and have its normal affect on boot. That is because cloud-init previously raised an exception when more than one file in /run/net*.conf declared the same DEVICE. Changes to isc-dhcp and initramfs-tools have changed their behavior and cloud-init has to adjust to allow DEVICE6= and DEVICE= in separate files. [Test Case] Boot a system on a network with both ipv4 and ipv6 dhcp servers, and pass kernel command line with: ip=dhcp ip6=dhcp [Regression Potential] Regression seems unlikely as this is relaxing a check. Where previously an exception would have been raised, cloud-init will now go on. So it seems most likely, something that didn't work before (due to raised exception) would now still not work, but with failures. That is not expected, but that would likely be where regressions were found. === End SRU Template === In changes made under bug 1621615 (specifically a1cdebdea), we now expect that there may be a 'ip6=' argument on the kernel command line. The changes made did not test the case where there is 'ip6=' and no 'ip='. The code currently will return with no network configuration found if there is only ip6=... Related bugs: * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1639930/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line
** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Status: New => In Progress ** Changed in: cloud-init (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1639930 Title: initramfs network configuration ignored if only ip6= on kernel command line Status in cloud-init: Confirmed Status in MAAS: New Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: In Progress Status in cloud-init source package in Yakkety: Confirmed Bug description: In changes made under bug 1621615 (specifically a1cdebdea), we now expect that there may be a 'ip6=' argument on the kernel command line. The changes made did not test the case where there is 'ip6=' and no 'ip='. The code currently will return with no network configuration found if there is only ip6=... Related bugs: * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1639930/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line
This bug was fixed in the package cloud-init - 0.7.8-61-g2d2ec70-0ubuntu1 --- cloud-init (0.7.8-61-g2d2ec70-0ubuntu1) zesty; urgency=medium * debian/grub-legacy-ec2.install: install post(inst|rm) files correctly. [Simon Deziel] (LP: #1581416) * New upstream snapshot. - OpenStack: extend physical types to include hyperv, hw_veb, vhost_user. [Scott Moser] (LP: #1642679) - tests: fix assumptions that expected no eth0 in system. [Scott Moser] (LP: #1644043) - net/cmdline: Consider ip= or ip6= on command line not only ip= [Scott Moser] (LP: #1639930) - Just use file logging by default [Joshua Harlow] (LP: #1643990) - Improve formatting for ProcessExecutionError [Wesley Wiedenmeier] - flake8: fix trailing white space [Scott Moser] - Doc: various documentation fixes [Sean Bright] - cloudinit/config/cc_rh_subscription.py: Remove repos before adding [Brent Baude] - packages/redhat: fix rpm spec file. [Scott Moser] - main: set TZ in environment if not already set. [Ryan Harper] - Azure: No longer rely on walinux agent. [Scott Moser] (LP: #1538522) - disk_setup: Use sectors as unit when formatting MBR disks with sfdisk. [Daniel Watkins] (LP: #1460715) -- Scott MoserMon, 28 Nov 2016 16:08:09 -0500 ** Changed in: cloud-init (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1639930 Title: initramfs network configuration ignored if only ip6= on kernel command line Status in cloud-init: Confirmed Status in MAAS: New Status in cloud-init package in Ubuntu: Fix Released Bug description: In changes made under bug 1621615 (specifically a1cdebdea), we now expect that there may be a 'ip6=' argument on the kernel command line. The changes made did not test the case where there is 'ip6=' and no 'ip='. The code currently will return with no network configuration found if there is only ip6=... Related bugs: * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1639930/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line
** Also affects: maas Importance: Undecided Status: New ** Tags added: maas-ipv6 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1639930 Title: initramfs network configuration ignored if only ip6= on kernel command line Status in cloud-init: Confirmed Status in MAAS: New Status in cloud-init package in Ubuntu: Confirmed Bug description: In changes made under bug 1621615 (specifically a1cdebdea), we now expect that there may be a 'ip6=' argument on the kernel command line. The changes made did not test the case where there is 'ip6=' and no 'ip='. The code currently will return with no network configuration found if there is only ip6=... Related bugs: * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1639930/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp