I am trying to understand why my server is failing to connect to the metadata server (and thus not able to log in with the SSH key).
Similar problems online seem to be caused by Security Group problems, that I am confident is not the problem here.
It is a single host, with IP of 192.168.160.100. The guest is given a fixed IP of 10.225.134.63. The network has a neutron DHCP server at 10.225.134.64.
On the host, I have run the following commands,
# curl http://192.168.160.100:8775
1.0
...
2008-09-01
2009-04-04
# curl http://169.254.169.254
curl: (7) Failed connect to 169.254.169.254:80; No route to host
/etc/neutron/metadata_agent.ini
nova_metadata_ip = 192.168.160.100
/etc/nova/nova.conf
metadata_host=192.168.160.100
Start up log
cloud-init[827]: Cloud-init v. 0.7.5 running 'init' at Fri, 29 Sep 2017 09:50:08 +0000. Up 6.40 seconds.
cloud-init[827]: ci-info: +++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++
cloud-init[827]: ci-info: +--------+------+---------------+---------------+-------------------+
cloud-init[827]: ci-info: | Device | Up | Address | Mask | Hw-Address |
cloud-init[827]: ci-info: +--------+------+---------------+---------------+-------------------+
cloud-init[827]: ci-info: | lo: | True | 127.0.0.1 | 255.0.0.0 | . |
cloud-init[827]: ci-info: | eth0: | True | 10.225.134.63 | 255.255.240.0 | fa:16:3e:0b:36:43 |
cloud-init[827]: ci-info: +--------+------+---------------+---------------+-------------------+
cloud-init[827]: ci-info: ++++++++++++++++++++++++++++++++Route info+++++++++++++++++++++++++++++++++
cloud-init[827]: ci-info: +-------+--------------+--------------+---------------+-----------+-------+
cloud-init[827]: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
cloud-init[827]: ci-info: +-------+--------------+--------------+---------------+-----------+-------+
cloud-init[827]: ci-info: | 0 | 0.0.0.0 | 10.225.128.1 | 0.0.0.0 | eth0 | UG |
cloud-init[827]: ci-info: | 1 | 10.225.128.0 | 0.0.0.0 | 255.255.240.0 | eth0 | U |
cloud-init[827]: ci-info: +-------+--------------+--------------+---------------+-----------+-------+
cloud-init[827]: url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: unexpected error ['NoneType' object has no attribute 'status_code']
cloud-init[827]: url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: unexpected error ['NoneType' object has no attribute 'status_code']
cloud-init[827]: url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: unexpected error ['NoneType' object has no attribute 'status_code']
cloud-init[827]: DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 120 seconds
cloud-init[827]: url_helper.py[WARNING]: Calling 'http://10.225.134.64//latest/meta-data/instance-id' failed [0/120s]: unexpected error ['NoneType' object has no attribute 'status_code']
cloud-init[827]: url_helper.py[WARNING]: Calling 'http://10.225.134.64//latest/meta-data/instance-id' failed [1/120s]: unexpected error ['NoneType' object has no attribute 'status_code']
cloud-init[827]: url_helper.py[WARNING]: Calling 'http://10.225.134.64//latest/meta-data/instance-id' failed [2/120s]: unexpected error ['NoneType' object has no attribute 'status_code']
...
cloud-init[827]: url_helper.py[WARNING]: Calling 'http://10.225.134.64//latest/meta-data/instance-id' failed [119/120s]: unexpected error ['NoneType' object has no attribute 'status_code']
cloud-init[827]: DataSourceCloudStack.py[CRITICAL]: Giving up on waiting for the metadata from ['http://10.225.134.64//latest/meta-data/instance-id'] after 126 seconds
Best Answer
It turns out that some routes were missing in the Management Network namespace. They were added using the following commands.