cloud-init 17.1 setting eth0 to manual start when launching instance in private subnet AWS EC2

[Pieter de Bruin]

AWS EC2 - No network config specified on this AMI by default

Launching new suse-sles-12-sp3-v20171107-hvm-ssd-x86_64 (ami-518b2628) within a private subnet (ie no public IP allocation) AMI located in Region eu-west-1, results in the network config script for eth0 being set to manual start:

BOOTPROTO=dhcp
MTU=9000
REMOTE_IPADDR=
STARTMODE=manual
CLOUD_NETCONFIG_MANAGE=yes
USERCONTROL=no
ETHTOOL_OPTIONS=

Network will start on the first launch but fail on subsequent restarts or stop and starts since the script is set to manual. This only happens when the instance is launched without a public IP (within a private subnet).

Output of cloud-init.log where config is applied:

2017-11-19 05:57:29,742 - stages.py[INFO]: Applying network configuration from ds bringup=True: {'version': 1, 'config': [{'subnets': [], 'type': 'physical', 'name': 'eth0', 'mac_address': '06:9d:49:56:d4:d8'}]}
iface eth0 inet manual
 into {'lo': {'auto': True, 'ipv6': {}}, 'eth0': {'ipv6': {}}}

Also noticed the following error in the cloud-init-output.log:

2017-11-19 06:44:32,421 - __init__.py[WARNING]: apply_network_config is not currently implemented for distribution '<class 'cloudinit.distros.sles.Distro'>'. Attempting to use apply_network

Downgraded cloud-init to version 7.9 on the instance and created a new AMI, this works fine and the network script is set to STARTMODE=onboot, also no error in cloud-init-output.log.

[Scott Moser (smoser)]

Robert, could you look at this?
I think you might even have filed a fix for it.

[Robert Schweikert (rjschwei)]

New SUSE AMIs have been released, see [1] [2]

[3] Addresses the issue

[1] https://forums.suse.com/showthread.php?10228-New-SLES-12-SP3-EC2-AMI-network-scripts-issues
[2] https://www.suse.com/communities/blog/ooops-v20171107-may-spell-network-trouble-aws-ec2/
[3] https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/334241

[Dan Watkins (oddbloke)]

Hi Pieter,

Thanks for filing this bug! It looks to me from the above comments like this is fixed in more recent releases of cloud-init. If you disagree, please do set this bug back to New (with explanation, of course!).

Thanks!

Dan

[Robert Schweikert (rjschwei)]

The patch to address this exact bug was never merged upstream and was only available in the openSUSE and SUSE Linux Enterprise Server packages. As of version 18.4 the code path for openSUSE and SLES was switched to use the sysconfig renderer where this problem no longer occurs. This bug should be closed.

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/3061