-
Notifications
You must be signed in to change notification settings - Fork 835
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eni rendering dhcp6 writes aliases fails to bring up dhcp6 #2791
Comments
Launchpad user Launchpad Janitor(janitor) wrote on 2017-02-04T03:49:52.859201+00:00 This bug was fixed in the package cloud-init - 0.7.9-19-ge987092-0ubuntu1 cloud-init (0.7.9-19-ge987092-0ubuntu1) zesty; urgency=medium
-- Scott Moser smoser@ubuntu.com Fri, 03 Feb 2017 21:54:39 -0500 |
Launchpad user Chris Halse Rogers(raof) wrote on 2017-03-07T23:25:33.153557+00:00 Hello Scott, or anyone else affected, Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-48-g1c795b9-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 on 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! |
Launchpad user Chris Halse Rogers(raof) wrote on 2017-03-07T23:33:54.392627+00:00 Hello Scott, or anyone else affected, Accepted cloud-init into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-48-g1c795b9-0ubuntu1~16.10.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 on 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! |
Launchpad user Scott Moser(smoser) wrote on 2017-03-08T20:41:29.853694+00:00 ami-6b6f4b0e ubuntu/images-testing-dev/hvm-ssd/ubuntu-xenial-16.04-testing-amd64-server-20170307 I launched an instance in an EC2 region (us-east-2) into a subnet with configured ipv6. $ rel=$(lsb_release -sc) just show the network info to show the ipv6 section.$ python3 -c 'from cloudinit import ec2_utils; print(ec2_utils.get_instance_metadata()["network"])' I then set default networking for cloud-init to attempt both ipv4 and ipv6. $ ADDR=$(cat /sys/class/net/eth0/address)
Then, clean the instance, and reboot. $ sudo rm -Rf /var/log/cloud-init /var/lib/cloud When you go back in, look /etc/network/interfaces.d/50-cloud-init.cfgand verify it has an ipv6 address and a dhclient6 running.$ grep -v "^[#]." /etc/network/interfaces.d/50-cloud-init.cfg | grep . $ ip address show dev eth0 $ ps axw | grep [d]hclient |
Launchpad user Scott Moser(smoser) wrote on 2017-03-08T20:48:55.204356+00:00 ami-6b6f4b0e ubuntu/images-testing-dev/hvm-ssd/ubuntu-xenial-16.04-testing-amd64-server-20170307 I launched an instance in an EC2 region (us-east-2) into a subnet with configured ipv6. $ rel=$(lsb_release -sc) just show the network info to show the ipv6 section.$ python3 -c 'from cloudinit import ec2_utils; print(ec2_utils.get_instance_metadata()["network"])' I then set default networking for cloud-init to attempt both ipv4 and ipv6. $ ADDR=$(cat /sys/class/net/eth0/address)
Then, clean the instance, and reboot. $ sudo rm -Rf /var/log/cloud-init /var/lib/cloud When you go back in, look /etc/network/interfaces.d/50-cloud-init.cfgand verify it has an ipv6 address and a dhclient6 running.$ grep -v "^[#]." /etc/network/interfaces.d/50-cloud-init.cfg | grep . $ grep INFO.*network /var/log/cloud-init.log | head -n 1 $ ip address show dev eth0 $ ps axw | grep [d]hclient |
Launchpad user Launchpad Janitor(janitor) wrote on 2017-03-16T16:18:49.500475+00:00 This bug was fixed in the package cloud-init - 0.7.9-48-g1c795b9-0ubuntu1~16.04.1 cloud-init (0.7.9-48-g1c795b9-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
-- Scott Moser smoser@ubuntu.com Mon, 06 Mar 2017 16:34:10 -0500 |
Launchpad user Brian Murray(brian-murray) wrote on 2017-03-16T16:19:12.127922+00:00 The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. |
Launchpad user Launchpad Janitor(janitor) wrote on 2017-03-16T16:19:33.912058+00:00 This bug was fixed in the package cloud-init - 0.7.9-48-g1c795b9-0ubuntu1~16.10.1 cloud-init (0.7.9-48-g1c795b9-0ubuntu1~16.10.1) yakkety; urgency=medium
-- Scott Moser smoser@ubuntu.com Mon, 06 Mar 2017 16:37:28 -0500 |
Launchpad user Ben Howard(darkmuggle-deactivatedaccount) wrote on 2017-03-23T21:40:22.479579+00:00 Reported bug #1675571 as a regression. Changing from eth0:1 means that hosts with no ipv6 addresses on Ubuntu 16.04 do not get /etc/resolv.conf populated with name servers. |
Launchpad user Scott Moser(smoser) wrote on 2017-09-23T02:14:53.740831+00:00 This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New Thank you. |
This bug was originally filed in Launchpad as LP: #1657940
Launchpad details
Launchpad user Scott Moser(smoser) wrote on 2017-01-20T02:00:57.582306+00:00
=== Begin SRU Template ===
[Impact]
cloud-init rendered ENI (/etc/network/interfaces) configuration using
"aliases" (eth0:1). That fails in some scenarios to bring up all interfaces
on boot.
Most specifically problematic is dhcp with ipv4 and dhcp with ipv6.
In that case ipv6 dhcp just would not come up on boot.
[Test Case]
There are unit tests to verify that the new network configuration
is written as expected. Additionally, this is now using the same
ENI rendering format that curtin uses, which has good test cases
in its 'vmtest'.
[Regression Potential]
Users who had done:
ifup eth0:1
will no longer be able to do that. However now this will reliably work:
ifup eth0
to bring up all ip addresses on eth0.
=== End SRU Template ===
Currently, a config like this:
| version: 1
| config:
| - 'type': 'physical'
| 'name': 'iface0'
| 'subnets':
| - {'type': 'dhcp4'}
| - {'type': 'dhcp6'}
Will render:
| auto lo
| iface lo inet loopback
|
| auto iface0
| iface iface0 inet dhcp
| post-up ifup iface0:1
|
|
| auto iface0:1
| iface iface0:1 inet6 dhcp
Below is an example test case that shows the output.
Heres the problem:
$ sudo sh -c 'ifdown eth0; ifup eth0'
$ sudo sh -c 'ifdown eth0; ifup eth0'
Killed old client process
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/06:b3:0a:3a:2d:e3
Sending on LPF/eth0/06:b3:0a:3a:2d:e3
Sending on Socket/fallback
DHCPRELEASE on eth0 to 172.31.16.1 port 67 (xid=0x32b625f1)
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/06:b3:0a:3a:2d:e3
Sending on LPF/eth0/06:b3:0a:3a:2d:e3
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xa4d5f301)
DHCPREQUEST of 172.31.29.161 on eth0 to 255.255.255.255 port 67 (xid=0x1f3d5a4)
DHCPOFFER of 172.31.29.161 from 172.31.16.1
DHCPACK of 172.31.29.161 from 172.31.16.1
bound to 172.31.29.161 -- renewal in 1801 seconds.
Failed to bring up eth0:1.
Failed to bring up eth0.
$ sudo ifup -v eth0:1
Parsing file /etc/network/interfaces.d/50-cloud-init.cfg
Parsing file /etc/network/interfaces.d/60-ipv6.cfg
Configuring interface eth0:1=eth0:1 (inet6)
/bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/ethtool
run-parts: executing /etc/network/if-pre-up.d/ifenslave
run-parts: executing /etc/network/if-pre-up.d/vlan
/sbin/modprobe -q net-pf-10 > /dev/null 2>&1 || true # ignore failure.
/sbin/sysctl -q -e -w net.ipv6.conf.eth0:1.accept_ra=1
/bin/ip link set dev eth0:1 up
/lib/ifupdown/wait-for-ll6.sh
/sbin/dhclient -1 -6 -pf /run/dhclient6.eth0:1.pid -lf /var/lib/dhcp/dhclient6.eth0:1.leases -I -df /var/lib/dhcp/dhclient.eth0:1.leases eth0:1
--- a/tests/unittests/test_net.py
+++ b/tests/unittests/test_net.py
@@ -813,6 +813,27 @@ class TestEniRoundTrip(TestCase):
self.assertEqual(
expected, [line for line in found if line])
The text was updated successfully, but these errors were encountered: