Static network config bug in Amazon Linux on-prem vmware

Hello,
Thanks for the feedback and the patch. I believe I understand the issue. One thing I wanted to make sure of is, what do you have set in your user-data for the VM? Below is an example of the options for a static configuration in the user-data for cloud-init:

network:
  version: 1
  config:
    - type: physical
      name: interface0
      mac_address: 00:11:22:33:44:55
      subnets:
         - type: static
           address: 192.168.23.14/24
           gateway: 192.168.23.1

For the rendering, it should be able to use sysconfig to make the network configuration. What version of cloud-init are you using on your VM?

-Heath

Hi Heath,
thanks for your answer. Our user-data contains only 'users' info and 'write_files' keys and meta-data contains just the static network config.
Both configs are written exactly as described in this guide:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html

$ cloud-init -v
/usr/bin/cloud-init 19.3-3.amzn2

$ dmesg | head -1
0.000000 Linux version 4.14.200-155.322.amzn2.x86_64 (mockbuild@ip-10-0-1-230) (gcc version 7.3.1 20180712 (Red Hat 7.3.1-10) (GCC)) #1 SMP Thu Oct 15 20:11:12 UTC 2020

This problem is also present in earlier versions of cloud-init.

I see the same issue with both the latest image (2.0.20200917.0) and 2.0.20200722.0. I don't have access to previous images to test. Not sure if it matters, but I am specifically using the KVM variant.

Are you suggesting that the documentation is out of date and that you now have to include the follow for a static IP config?

network:
version: 1
config:
- type: physical
name: interface0
mac_address: 00:11:22:33:44:55
subnets:
- type: static
address: 192.168.23.14/24
gateway: 192.168.23.1

Just piping in to mention I have the same issue. I've tried the simple setup in the meta-data file as described in the AWS documentation and I've tried a seperate setup using the approach you describe (using a "network-config" file instead of the user-data"). Both end up at the same "Unable to render networking" error in the cloud-init-output.log file.

The workaround in utils.py mentioned would probably solve it but that means we either have to edit the Amazon VDI with every new version or set up some unconventional scripting to allow our cloud-init script to complete on first boot.

Edited by: markotting on Dec 9, 2020 6:54 AM

Thanks a lot - the error is gone after applying the patch and I can tell the file is applied noticing the hostname changed. But the IP config in this metadata file was not applied. Any idea?

$ more metadata.yaml
#cloud-config
local-hostname: uitlal2t04.mcs.company.com
network-interfaces: |
auto eth0
iface eth0 inet static
address 10.1.38.28
network 10.1.38.0
netmask 255.255.255.0
broadcast 10.1.38.255
gateway 10.1.38.254

I am using vmwareguestinfo data source

How are you able to apply the patch at boot time? I'm stuck trying to figure out how to boot the image with seed.iso and get a patched cloud-init version. I've got some automation to create vm's in hyper-v using this pattern but the workflow is broken since the network interfaces can't get configured.

This is sadly still broken with the latest 2.0.20210126.0 release.

The documentation in the README.cloud-init is broken, as is the document here:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html