- 新しい順
- 投票が多い順
- コメントが多い順
This used to work for me fine, but is broken now using the
https://cdn.amazonlinux.com/os-images/2.0.20200304.0/hyperv/amzn2-hyperv-2.0.20200304.0-x86_64.xfs.gpt.vhdx.zip
image. Seems like a regression somewhere. Just following the instructions here:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html
results in a network interface that is not configured and tries to use dhcp. I get the same error messages in /var/log/messages.
Edited by: wynnw on Mar 16, 2020 11:39 AM
Edited by: wynnw on Mar 16, 2020 12:07 PM
Thanks, that was the instructions I followed. The meta-data is followed, at least a little bit, since the hostname is set, and the user-data also, since the password is set for the ec2-user.
Let's hope it'll resolve in a future release
I was having the same problem with amzn2-vmware_esx-2.0.20200722.0-x86_64.xfs.gpt.ova, but when I used the same seed iso with amzn2-vmware_esx-2.0.20190612-x86_64.xfs.gpt.ova it worked perfectly.
Failed attempt with 20200722
cloud-init.log:Sep 04 21:45:03 cloud-init[6391]: stages.py[INFO]: Applying network configuration from ds bringup=False: {'version': 1, 'config': [{'subnets': [{'control': 'auto', 'dns_nameservers': ['10.2.5.21', '9.9.9.9'], '_orig_eni_name': 'eth0', 'broadcast': '10.2.5.255', 'netmask': '255.255.255.0', 'address': '10.2.5.77', 'type': 'static', 'gateway': '10.2.5.21'}], 'type': 'physical', 'name': 'eth0'}]}
cloud-init.log:Sep 04 21:45:03 cloud-init[6391]: stages.py[ERROR]: Unable to render networking. Network config is likely broken: No available network renderers found. Searched through list: ['eni', 'sysconfig', 'netplan']
Successful attempt with 20190612
cloud-init.log:Sep 04 21:55:04 cloud-init[6405]: stages.py[INFO]: Applying network configuration from ds bringup=False: {'version': 1, 'config': [{'subnets': [{'control': 'auto', 'dns_nameservers': ['10.2.5.21', '9.9.9.9'], '_orig_eni_name': 'eth0', 'broadcast': '10.2.5.255', 'netmask': '255.255.255.0', 'address': '10.2.5.77', 'type': 'static', 'gateway': '10.2.5.21'}], 'type': 'physical', 'name': 'eth0'}]}
cloud-init.log:Sep 04 21:55:04 cloud-init[6405]: util.py[DEBUG]: Writing to /etc/sysconfig/network-scripts/ifcfg-eth0 - wb: [644] 249 bytes
What's mentioned here is a real issue in cloud-init, see below for a possible fix.
https://forums.aws.amazon.com/thread.jspa?threadID=330409&tstart=0
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
The linked reply with a diff to fix cloud-init does look like it would work, but there's no way to patch this at boot time that I can see. I'm really stuck trying to figure out how to work around this, and I'm still stuck loading a two year old image and then upgrading it. Really frustrating - I've tried all sorts of yaml config variants for the seed.iso with no luck.
And finally it's fixed in 2.0.20210721.2.
Make sure to use dns_nameservers and dns_search, not dns-nameservers/dns-search.
関連するコンテンツ
- AWS公式更新しました 2年前
Has there been any updates yet?