Ask Your Question
1

ssh keypair cloud-init error

asked 2015-03-31 11:23:39 -0600

kvk_vijay gravatar image

updated 2015-03-31 14:16:01 -0600

dbaxps gravatar image

when launching the instance it's launching without the ssh key added into the authorized_keys file . This is the error from cloud-init log

Cloud-init v. 0.7.5 running 'init-local' at Tue, 31 Mar 2015 15:42:15 +0000. Up 444.34 seconds.
Cloud-init v. 0.7.5 running 'init' at Tue, 31 Mar 2015 15:43:21 +0000. Up 510.62 seconds.
ci-info: ++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: | Device |  Up  |   Address    |      Mask     |     Hw-Address    |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: |   lo   | True |  127.0.0.1   |   255.0.0.0   |         .         |
ci-info: |  eth0  | True | 192.168.1.11 | 255.255.255.0 | fa:16:3e:e7:61:31 |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: +++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++++
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | Route | Destination |   Gateway   |    Genmask    | Interface | Flags |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: |   0   | 192.168.1.0 |   0.0.0.0   | 255.255.255.0 |    eth0   |   U   |
ci-info: |   1   |   0.0.0.0   | 192.168.1.1 |    0.0.0.0    |    eth0   |   UG  |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
2015-03-31 11:43:56,658 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: bad status code [500]
2015-03-31 11:43:57,878 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: bad status code [500]
2015-03-31 11:43:59,098 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: bad status code [500]
2015-03-31 11:44:00,297 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]: bad status code [500]
2015-03-31 11:44:01,495 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: bad status code [500]
2015-03-31 11:44:02,710 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [6/120s]: bad status code [500]
2015-03-31 11:44:04,900 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [8/120s]: bad status code [500]
2015-03-31 11:44:07,100 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [10/120s]: bad status code
edit retag flag offensive close merge delete

Comments

can you provide a bit of information on your environment, and whether you have admin access to manipulate configuration files. Does this only happen on this particular image or all images?

omar-munoz gravatar imageomar-munoz ( 2015-03-31 16:06:27 -0600 )edit

Environment is 1. controller node 2. nework node 3. compute node installed on ubuntu 14.04 VM's juno release. i am getting this error for all the images downloaded from redhat & ubuntu as well.

Yes i do have access to change the configuration files

kvk_vijay gravatar imagekvk_vijay ( 2015-04-01 03:43:31 -0600 )edit
add a comment

2 answers

Sort by ยป oldest newest most voted
0

answered 2015-04-01 13:14:36 -0600

omar-munoz gravatar image

Can you try using the cirros image just to validate it's not an image issue. If you don't have it in your environment just download and upload it with the following commands. Then just launch an instance and see if the metadata populates. 

wget -P /tmp/images http://cdn.download.cirros-cloud.net/0.3.3/cirros-0.3.3-x86_64-disk.img

glance image-create --name "cirros-0.3.3-x86_64" --file /tmp/images/cirros-0.3.3-x86_64-disk.img --disk-format qcow2 --container-format bare --is-public True --progress

Looking to the nova.conf confirm the metadata api is enabled. And the port 8775 is listening please confirm using this command: netstat -nap | grep 8775 or whatever port you're using.

If you access the instance via the console does 'curl http://169.254.169.254/latest/meta-data' return any results?

also if you are using neutron can you run 'ip netns' to see if it's accessible from your router. One more question. Please run 

# ip netns list 
qrouter-cb80b040-f13f-4a67-a39e-353b1c873a0d 
qdhcp-166d9651-d299-47df-a5a1-b368e87b612f
# ip netns exec qrouter-cb80b040-f13f-4a67-a39e-353b1c873a0d iptables -L -t nat
# ip netns exec qrouter-cb80b040-f13f-4a67-a39e-353b1c873a0d curl http://169.254.169.254/
edit flag offensive delete link more
add a comment
0

answered 2015-04-07 07:50:10 -0600

kvk_vijay gravatar image

I had a problem with cirros iamge also . Found out as my VM tenant can't reach that network . that's why

edit flag offensive delete link more
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

subscribe to rss feed

Stats

Asked: 2015-03-31 11:23:39 -0600

Seen: 3,050 times

Last updated: Apr 07 '15

Related questions

Why does Metadata Agent keep falling over?

Metadata query hanging [closed]

Unable to login to new instance via console/SSH [closed]

tripleo queens metadata 404 [closed]

Unable to ssh with key pair [closed]

metadata working, user-data not

neutron.agent.metadata.agent [-] Failed reporting state!

Problem with metadata

why neutron metadata proxy is running with the router id?

Metadata Proxy server() got an unexpected keyword argument 'socket_timeout'