ssh public key can't be injected into instance
I installed ICEhouse on Window8.1 Host and VMware VMs - 4 node ( Controller, Compute, Network, Block Storage).
But I cannot connect to the instance with ssh private key. So I check instance console log and check like following.
when instance is launched, (I checked console log lists) even though instance connects to http://169.254.169.254/2009-04-04/ins... , the log shows fail message.
checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 18.98. request failed
failed 2/20: up 21.51. request failed
failed 3/20: up 23.76. request failed
failed 4/20: up 26.02. request failed
failed 5/20: up 28.28. request failed
failed 6/20: up 30.51. request failed
failed 7/20: up 32.93. request failed
failed 8/20: up 35.16. request failed
failed 9/20: up 37.38. request failed
As I know, when instance is made, nova-api-metadata service can be connected and then ssh public key is injected.
So I checked ssh pulbic key is not injected into instance correctly.
=== sshd host keys ===
-----BEGIN SSH HOST KEY KEYS-----
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgnKr+B121EUSFAhTWSljdvK8RjBZfm7FhcKtMq0HpIHukUdx06gwqJIcAPztF2f3PsyvNwunVuTkoehvH+9Dnu/IfXBsESY1LFzrIjtINLxOzh6zYnAt8DQbUmINEQSXykbUWfsX1c+tn6cgkXSX2kVEBv7qRgOHuDGpR+vpj146Gi0= root@cirros
ssh-dss AAAAB3NzaC1kc3MAAACBAKF8eavLiWdZLzr9ODrya0QTvEv+QCh4p58pzNAVduiy5N32m3sSuyLTfa0gHP+b9D0QmbCfQVNXj1uLW/sUMCe5/0leIwLhQOn1B4yAkPQKEXiXTTAepvKBa9Lyotv/0SNyaHICrgBsC8ElK8XR1ArX6c6fyP03O32/+g/g3IBNAAAAFQCWQXaKsZz7qYh7tk8dakZPDzXkuQAAAIEAm0/CIfBy5AhhPiqVbOoBMBYeCofAQ0mAKjv7g8IVWYGosp8/lspqYP6975DBF4wsQq67eTl6KRI6oFDtJdHOcCy0ATcx/f/eoJjM85E16fkz+VfXEcKFDFG/XHJeUfsBjScmC2N0z8m90GTijcO6r88pnG2QCp0cSNXKr7ij7nIAAACAP9c62Q3JZxMYTtdoLhwC0EY85dEBxmaUO2mmDXajTKxNPrPFAHuUO+lInw9O8JAhzEwo3mo7chTesoXWziUQB3uhkhTw3j8JHN5HBBvCJtzcRaisp1NhwwaR9leiBGdF+XicPOo4okzZiCx1pAlVEvRM0PXfMqIvgc0ZvvfjyHw= root@cirros
-----END SSH HOST KEY KEYS-----
So I checked metadata section in admin guide, http://docs.openstack.org/admin-guide... , the guide said in multi-host mode, I should inject metadata_host = 127.0.0.1 in /etc/nova/nova.conf.
Is this correct configuration? and I am not sure the setting should be in control node or compute node.
In network node
$ ip netns exec qrouter-router-id iptables -t nat -S | grep 169.254
-A neutron-l3-agent-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 9697
$ ip netns exec qrouter-router-id netstat -antp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:9697 0.0.0.0:* LISTEN 42020/python
$ ps -ef | grep 42020
root 42020 1 0 17:03 ? 00:00:00 /usr/bin/python /usr/bin/neutron-ns-metadata-proxy --pid_file=/var/lib/neutron/external/pids/166fa743-68e0-41ee-961f-91d039999fa2.pid --metadata_proxy_socket=/var/lib/neutron/metadata_proxy --router_id=166fa743-68e0-41ee-961f-91d039999fa2 --state_path=/var/lib/neutron --metadata_port=9697 --verbose --log-file=neutron-ns-metadata-proxy-166fa743-68e0-41ee-961f-91d039999fa2.log --log-dir=/var/log/neutron
In Controller Node
root@controller:~# netstat -lntp | grep 8775
tcp 0 0 0.0.0.0:8775 0.0.0.0:* LISTEN 12893/python
root@controller:~# ps -ef | grep 12893
nova 12893 1 1 22:28 ? 00:00:32 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 12899 12893 0 22:28 ? 00:00:00 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 12900 12893 0 22:28 ? 00:00:07 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 12907 12893 0 22:28 ? 00:00:00 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
On my Multi Node IceHouse ML2&OVS&VXLAN system in nova.conf
metadata_host=192.168.1.127 ( IP of Controller). Create any ssh keypair in Dashboard and assign to instance. You have another problem - access to nova metadata server.
Message should look like checking http://169.254.169.254/2009-04-04/met...
@dbaxps nova.conf in all nodes added "metadata_host=(IP of Controller)" ?
It's correct. Does CirrOS VM still complaining 169.254.169.254 at booting up ?
@dbaxps yes, the problem not fixed..