[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
** 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
[Yahoo-eng-team] [Bug 1621615] Re: network not configured when ipv6 netbooted into cloud-init
My currently-pending MPs address the issue and work in conjunction with the new fixes for Bug#1621507: https://code.launchpad.net/~lamont/cloud-init/+git/bug-1621615-device6/+merge/309718 https://code.launchpad.net/~lamont/cloud-initramfs-tools/bug-1621615-device6/+merge/309719 These need to land in zesty, and get SRUed to xenial and yakkety. ** Changed in: maas Status: Fix Released => In Progress ** Changed in: cloud-init Status: Fix Committed => Confirmed ** Changed in: cloud-init (Ubuntu) Status: Fix Released => Confirmed ** Changed in: cloud-init (Ubuntu Xenial) Status: Fix Released => Confirmed ** Changed in: cloud-initramfs-tools (Ubuntu) Status: Fix Released => Confirmed ** Changed in: cloud-initramfs-tools (Ubuntu Xenial) Status: Fix Released => Confirmed ** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: cloud-initramfs-tools (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: maas Milestone: 2.1.0 => 2.1.1 -- 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/1621615 Title: network not configured when ipv6 netbooted into cloud-init Status in cloud-init: Confirmed Status in MAAS: In Progress Status in cloud-init package in Ubuntu: Confirmed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-init source package in Xenial: Confirmed Status in cloud-initramfs-tools source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: New Status in cloud-initramfs-tools source package in Yakkety: New Bug description: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507 talks of how IPv6 netboot with iscsi root disk doesn't work, blocking IPv6-only MAAS. After I hand-walked busybox through getting an IPv6 address, everything worked just fine until cloud-init couldn't fetch the instance data, because it insisted on bringing up the interface in IPv4, and there is no IPv4 DHCP on that vlan. Please work with initramfs and friends on getting IPv6 netboot to actually configure the interface. This may be as simple as teaching it about "inet6 dhcp" interfaces, and bolting the pieces together. Note that "use radvd" is not really an option for our use case. Related bugs: * 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) [Impact] It is not possible to enlist, commmission, or deploy with MAAS in an IPv6-only environment. Anyone wanting to netboot with a network root filesystem in an IPv6-only environment is affected. This upload addresses this by accepting, using, and forwarding any IPV6* variables from the initramfs boot. (See https://launchpad.net/bugs/1621507) [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your IPv6-only netbooting world. Pass the boot process an IPv6 address to fetch instance-data from, and see it fail to configure the network. [Regression Potential] 1) If the booting host is in a dual-boot environment, and the instance-dat URL uses a hostname that has both A and RRsets, the booting host may try to talk IPv6 to get instance data. If the instance-data providing host is only allowing that to happen over IPv4, it will fail. (It also represents a configuraiton issue on the providing host...) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1621615/+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 1621615] Re: network not configured when ipv6 netbooted into cloud-init
** Also affects: cloud-initramfs-tools (Ubuntu) Importance: Undecided Status: New ** No longer affects: cloud-initramfs-tools (Ubuntu) -- 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/1621615 Title: network not configured when ipv6 netbooted into cloud-init Status in cloud-init: In Progress Status in MAAS: New Status in cloud-init package in Ubuntu: Confirmed Status in cloud-init source package in Xenial: Fix Committed Bug description: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507 talks of how IPv6 netboot with iscsi root disk doesn't work, blocking IPv6-only MAAS. After I hand-walked busybox through getting an IPv6 address, everything worked just fine until cloud-init couldn't fetch the instance data, because it insisted on bringing up the interface in IPv4, and there is no IPv4 DHCP on that vlan. Please work with initramfs and friends on getting IPv6 netboot to actually configure the interface. This may be as simple as teaching it about "inet6 dhcp" interfaces, and bolting the pieces together. Note that "use radvd" is not really an option for our use case. Related bugs: * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses [Impact] It is not possible to enlist, commmission, or deploy with MAAS in an IPv6-only environment. Anyone wanting to netboot with a network root filesystem in an IPv6-only environment is affected. This upload addresses this by accepting, using, and forwarding any IPV6* variables from the initramfs boot. (See https://launchpad.net/bugs/1621507) [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your IPv6-only netbooting world. Pass the boot process an IPv6 address to fetch instance-data from, and see it fail to configure the network. [Regression Potential] 1) If the booting host is in a dual-boot environment, and the instance-dat URL uses a hostname that has both A and RRsets, the booting host may try to talk IPv6 to get instance data. If the instance-data providing host is only allowing that to happen over IPv4, it will fail. (It also represents a configuraiton issue on the providing host...) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1621615/+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 1311700] Re: "Setting oauth clockskew" messages on booting node; slows down boot
This is a cloud-init bug. ** Changed in: maas Status: Incomplete => Invalid -- 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/1311700 Title: "Setting oauth clockskew" messages on booting node; slows down boot Status in cloud-init: Triaged Status in MAAS: Invalid Bug description: On booting nodes for enlistment, commissioning, and starting, I sometimes see repeated errors like this: 2014-04-23 14:15:50,622 - DataSourceMAAS.py[WARNING]: Setting oauth clockskew to -2 (See attached screen shot, too.) These scroll by, once every second or so, for about a minute before the node continues booting. Although a minute here or there isn't all THAT big of a deal, it would be nice to see this delay go away, particularly for occasions when I have to repeatedly test a node. Here's my version information: $ dpkg -l '*maas*'|cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-===--=== ii maas 1.5+bzr2252-0ubuntu1all MAAS server all-in-one metapackage ii maas-cli 1.5+bzr2252-0ubuntu1all MAAS command line API tool ii maas-cluster-controller 1.5+bzr2252-0ubuntu1all MAAS server cluster controller ii maas-common 1.5+bzr2252-0ubuntu1all MAAS server common files ii maas-dhcp 1.5+bzr2252-0ubuntu1all MAAS DHCP server ii maas-dns 1.5+bzr2252-0ubuntu1all MAAS DNS server ii maas-region-controller 1.5+bzr2252-0ubuntu1all MAAS server complete region controller ii maas-region-controller-min 1.5+bzr2252-0ubuntu1all MAAS Server minimum region controller ii python-django-maas 1.5+bzr2252-0ubuntu1all MAAS server Django web framework ii python-maas-client 1.5+bzr2252-0ubuntu1all MAAS python API client ii python-maas-provisioningserver 1.5+bzr2252-0ubuntu1all MAAS server provisioning libraries To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1311700/+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
