yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #85600
[Bug 1911922] Re: Failed to run Kubelet: could not init cloud provider "aws"
[Expired for cloud-init because there has been no activity for 60 days.]
** Changed in: cloud-init
Status: Incomplete => Expired
--
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/1911922
Title:
Failed to run Kubelet: could not init cloud provider "aws"
Status in cloud-init:
Expired
Bug description:
Hi,
I've created an AMI using packer and centos7.8 ISO. Launched a vm
using this AMI and unable to resolve to any URLs unless I restart
network service. I need to restart network.service everytime I reboot
my vm.
I had anothe AMI with the same ISO but cloud init 18.5 version and is
still working good.
Failed to run Kubelet: could not init cloud provider "aws": unable to determine AWS zone from cloud provider config or EC2 instance metadata: RequestError: send request failed
caused by: Get http://169.254.169.254/latest/meta-data/placement/availability-zone: dial tcp 169.254.169.254:80: connect: network is unreachable.
[root@ip-172-31-37-43 log]# curl google.com
curl: (6) Could not resolve host: google.com; Unknown error
[root@ip-172-31-37-43 log]# cat /etc/resolv.conf
# Generated by NetworkManager
search eu-west-2.compute.internal
I've verified neccessar outbound traffic is allowed.
I've attached the cloud-init collect logs tar file with this bug.
Cloud provider: AWS
Thanks,
Charan
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1911922/+subscriptions
References