Hi Anil, I met the same issue in my local devstack environment. Do you use proxy when you execute stack.sh script in your environment? If so, please try to set no_proxy parameter.
See also: https://answers.launchpad.net/devstack/+question/245480 Regards, Kaz From: Anil Rao <anil....@gigamon.com> Subject: [openstack-dev] [all] Cloud-init VM instance not coming up in a multi-node DevStack envionment Date: Thu, 2 Mar 2017 03:27:33 +0000 > Hi, > > I recently created a multi-node DevStack environment (based on stable/ocata) > made up of the following nodes: > > > - 1 Controller Node > > - 1 Network Node > > - 2 Compute Nodes > > All VM instances are only deployed on the 2 compute nodes. Neutron network > services are provided by the network node. > > I am able to create VMs and have them communicate with each other and also > with external (outside the DevStack environment) endpoints. > > However, I find that I am unable to successfully deploy a VM instance that is > based on cloud-init. As the following console log snippet shows, cloud-init > running inside a VM instance is unable to get the necessary meta-data and > hangs during VM instance startup. > > > 91.811361] cloud-init[977]: ci-info: > ++++++++++++++++++++++++++++++++++++++Net device > info+++++++++++++++++++++++++++++++++++++++ > [ 91.818689] cloud-init[977]: ci-info: > +--------+------+------------------------------+---------------+-------+-------------------+ > [ 91.825274] cloud-init[977]: ci-info: | Device | Up | Address > | Mask | Scope | Hw-Address | > [ 91.832763] cloud-init[977]: ci-info: > +--------+------+------------------------------+---------------+-------+-------------------+ > [ 91.839288] cloud-init[977]: ci-info: | lo | True | 127.0.0.1 > | 255.0.0.0 | . | . | > [ 91.857827] cloud-init[977]: ci-info: | lo | True | ::1/128 > | . | host | . | > [ 91.864806] cloud-init[977]: ci-info: | eth0 | True | > 192.168.1.10 | 255.255.255.0 | . | fa:16:3e:cf:a8:d8 | > [ 91.871433] cloud-init[977]: ci-info: | eth0 | True | > fe80::f816:3eff:fecf:a8d8/64 | . | link | fa:16:3e:cf:a8:d8 | > [ 91.878237] cloud-init[977]: ci-info: > +--------+------+------------------------------+---------------+-------+-------------------+ > [ 91.896344] cloud-init[977]: ci-info: > ++++++++++++++++++++++++++++++++Route IPv4 > info++++++++++++++++++++++++++++++++ > [ 91.903652] cloud-init[977]: ci-info: > +-------+-----------------+-------------+-----------------+-----------+-------+ > [ 91.912523] cloud-init[977]: ci-info: | Route | Destination | > Gateway | Genmask | Interface | Flags | > [ 91.930131] cloud-init[977]: ci-info: > +-------+-----------------+-------------+-----------------+-----------+-------+ > [ 91.936482] cloud-init[977]: ci-info: | 0 | 0.0.0.0 | > 192.168.1.1 | 0.0.0.0 | eth0 | UG | > [ 91.942651] cloud-init[977]: ci-info: | 1 | 169.254.169.254 | > 192.168.1.1 | 255.255.255.255 | eth0 | UGH | > [ 91.948624] cloud-init[977]: ci-info: | 2 | 192.168.1.0 | > 0.0.0.0 | 255.255.255.0 | eth0 | U | > [ 91.954798] cloud-init[977]: ci-info: > +-------+-----------------+-------------+-----------------+-----------+-------+ > [ 91.961102] cloud-init[977]: 2017-03-01 17:46:38,723 - > url_helper.py[WARNING]: Calling > 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: > bad status code [404] > [ 92.997374] cloud-init[977]: 2017-03-01 17:46:39,917 - > url_helper.py[WARNING]: Calling > 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: > bad status code [404] > [ 94.320985] cloud-init[977]: 2017-03-01 17:46:41,240 - > url_helper.py[WARNING]: Calling > 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: > bad status code [404] > [ 95.480615] cloud-init[977]: 2017-03-01 17:46:42,400 - > url_helper.py[WARNING]: Calling > 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]: > bad status code [404] > [ > ... > > [ 118.589843] cloud-init[977]: 2017-03-01 17:47:05,509 - > url_helper.py[WARNING]: Calling > 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [27/120s]: > bad status code [404] > [ 121.796946] cloud-init[977]: 2017-03-01 17:47:08,716 - > url_helper.py[WARNING]: Calling > 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [30/120s]: > bad status code [404] > [ 124.918111] cloud-init[977]: 2017-03-01 17:47:11,837 - > url_helper.py[WARNING]: Calling > 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [33/120s]: > bad status code [404] > [ 129.195778] cloud-init[977]: 2017-03-01 17:47:16,115 - > url_helper.py[WARNING]: Calling > 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [37/120s]: > bad status code [404] > > > I am not sure what needs to be done to ensure that the metadata endpoint is > accessible from inside the VM instance and was looking for some assistance. > Any pointer and/or suggestions would be most appreciated. > > Kind regards, > Anil __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
