This bug was fixed in the package cloud-init - 17.1-27-geb292c18-0ubuntu1~17.10.1
--------------- cloud-init (17.1-27-geb292c18-0ubuntu1~17.10.1) artful-proposed; urgency=medium * New upstream snapshot. - EC2: Limit network config to fallback nic, fix local-ipv4 only instances. (LP: #1728152) - Gentoo: Use "rc-service" rather than "service". [Carlos Konstanski] cloud-init (17.1-25-g17a15f9e-0ubuntu1~17.10.1) artful-proposed; urgency=medium * New upstream snapshot. - resizefs: Fix regression when system booted with root=PARTUUID= (LP: #1725067) - tools: make yum package installation more reliable - citest: fix remaining warnings raised by integration tests. - citest: show the class actual class name in results. - ntp: fix config module schema to allow empty ntp config (LP: #1724951) - tools: disable fastestmirror if using proxy [Joshua Powers] - schema: Log debug instead of warning when jsonschema is not available. (LP: #1724354) -- Chad Smith <chad.sm...@canonical.com> Tue, 31 Oct 2017 12:56:34 -0600 ** Changed in: cloud-init (Ubuntu Artful) 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/1728152 Title: EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Committed Status in cloud-init source package in Zesty: Fix Released Status in cloud-init source package in Artful: Fix Released Status in cloud-init source package in Bionic: Fix Released Bug description: === Begin SRU Template === [Impact] Support for configuration of IPV6 addresses on the primary network interface in EC2 changed behavior of the automatic network configuration. This changed behavior in 2 ways: a.) Instances with only a private ipv4 address would not get *any* ipv4 address. b.) Instances with multiple NICs attached at boot would get all NICs configured. Previously only the primary network interface would be configured by cloud-init. 'b' is not necessarily a bug for Artful. A new release can bring new behavior. However, the change of behavior was not intended and not desired for an SRU. In an effort to keep this behavior consistent across 16.04+ we will be changing the behavior of Artful to only configure the primary network interface. [Test Case] To verify this code is fixed for all cases involved: 1. Verify that instances without public ipv4 get an ipv4 address. * Launch an instance on EC2 without a public IPV4 address. * Verify the instance has its Ipv4 address configured via ssh and checking 'ip' output. 2. Verify no regression is done to public systems. * Launch an instance on EC2 with a public IPV4 address. * Verify the instance has its ipv4 address configured. 3. Verify only the primary NIC is configured (17.10 only) * Launch an instance on EC2 with multiple nics configured. * Verify that only the primary nic has configuration by default. For each of the above, verification entails inspection of network config (/etc/network/interfaces.d/* or /etc/netplan/) and also network state ('ip a' output). [Regression Potential] Regression in this area of code is certainly limited to EC2, and most likely limited to network configuration. Complete failure would show itself as no networking at all and a WARNING or stack trace on the console logs. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=XXXXXXXXXX === End SRU Template === With the following cloud-init configuration: system_info: network: renderers: ['netplan', 'eni', 'sysconfig'] network: version: 2 ethernets: id0: match: name: e* dhcp4: true dhcp6: true with version 17.1-18-gd4f70470-0ubuntu1 on ami-36a8754c, it writes out the following network configuration: # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: ens3: dhcp6: true match: macaddress: 02:14:13:66:8a:66 set-name: ens3 ---- This instance is in a (default) VPC with a private IPv4 address and no public IPv4 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1728152/+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