<div dir="ltr"><div><br></div>This can probably be useful too:<br><br>From network node<div><br><div># ip netns ls</div><div>qdhcp-1b982b98-62db-4c87-867b-0490bac8fb52</div><div>qrouter-c7e7ea00-a362-4f4f-9a1c-a54ac86eb3be</div>
<div><br></div></div><div><div># ps -x | grep metadata</div><div> 1469 ? S 0:00 /usr/bin/python /usr/bin/neutron-ns-metadata-proxy --pid_file=/var/lib/neutron/external/pids/6c91714c-c1aa-41d7-88ba-249df3a8368c.pid --metadata_proxy_socket=/var/lib/neutron/metadata_proxy --network_id=6c91714c-c1aa-41d7-88ba-249df3a8368c --state_path=/var/lib/neutron --metadata_port=80 --log-file=neutron-ns-metadata-proxy-6c91714c-c1aa-41d7-88ba-249df3a8368c.log --log-dir=/var/log/neutron</div>
<div> 5937 ? S 0:00 /usr/bin/python /usr/bin/neutron-ns-metadata-proxy --pid_file=/var/lib/neutron/external/pids/fa72c69b-2ca2-4d4d-ab8c-d6fa6e8e72d6.pid --metadata_proxy_socket=/var/lib/neutron/metadata_proxy --network_id=fa72c69b-2ca2-4d4d-ab8c-d6fa6e8e72d6 --state_path=/var/lib/neutron --metadata_port=80 --log-file=neutron-ns-metadata-proxy-fa72c69b-2ca2-4d4d-ab8c-d6fa6e8e72d6.log --log-dir=/var/log/neutron</div>
<div> 8108 ? S 0:00 /usr/bin/python /usr/bin/neutron-ns-metadata-proxy --pid_file=/var/lib/neutron/external/pids/c7e7ea00-a362-4f4f-9a1c-a54ac86eb3be.pid --metadata_proxy_socket=/var/lib/neutron/metadata_proxy --router_id=c7e7ea00-a362-4f4f-9a1c-a54ac86eb3be --state_path=/var/lib/neutron --metadata_port=9697 --log-file=neutron-ns-metadata-proxy-c7e7ea00-a362-4f4f-9a1c-a54ac86eb3be.log --log-dir=/var/log/neutron</div>
</div><div class="gmail_extra"><br><br><br><div class="gmail_quote">2014-06-14 20:38 GMT+03:00 Sergey Motovilovets <span dir="ltr"><<a href="mailto:motovilovets.sergey@gmail.com" target="_blank">motovilovets.sergey@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi, Mike.<div><br></div><div>There are no routes in my VM's except for the default one. Private subnet I'm using is <a href="http://192.168.0.0/24" target="_blank">192.168.0.0/24</a> with neutron router on 192.168.0.1.</div>
<div><br></div><div><div># route -n</div><div>Kernel IP routing table</div><div>Destination Gateway Genmask Flags Metric Ref Use Iface</div><div>0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0</div>
<div>192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0</div></div><div><br></div><div>Following is a part of Fedora cloud-init script output. Instance tries to get info from 169.254.169.254 and then switches to 192.168.0.2, which is an interface with dnsmasq injected by neutron. I guess, metadata service is supposed to listen on 192.168.0.2, but it's not.</div>
<div><span style="color:rgb(0,0,0);white-space:pre-wrap"><br></span></div><div><span style="color:rgb(0,0,0);white-space:pre-wrap">[ 61.409140] cloud-init[512]: 2014-06-14 17:23:53,183 - url_helper.py[WARNING]: Calling '<a href="http://169.254.169.254/2009-04-04/meta-data/instance-id" target="_blank">http://169.254.169.254/2009-04-04/meta-data/instance-id</a>' failed [50/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Request timed out. (timeout=50.0)]</span><br>
</div><div><pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">[ 112.463197] cloud-init[512]: 2014-06-14 17:24:44,237 - url_helper.py[WARNING]: Calling '<a href="http://169.254.169.254/2009-04-04/meta-data/instance-id" target="_blank">http://169.254.169.254/2009-04-04/meta-data/instance-id</a>' failed [101/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Request timed out. (timeout=50.0)]
[ 130.489916] cloud-init[512]: 2014-06-14 17:25:02,264 - url_helper.py[WARNING]: Calling '<a href="http://169.254.169.254/2009-04-04/meta-data/instance-id" target="_blank">http://169.254.169.254/2009-04-04/meta-data/instance-id</a>' failed [119/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Request timed out. (timeout=17.0)]
[ 131.494462] cloud-init[512]: 2014-06-14 17:25:03,266 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['<a href="http://169.254.169.254/2009-04-04/meta-data/instance-id" target="_blank">http://169.254.169.254/2009-04-04/meta-data/instance-id</a>'] after 120 seconds
[ 131.502647] cloud-init[512]: 2014-06-14 17:25:03,273 - url_helper.py[WARNING]: Calling '<a href="http://192.168.0.2//latest/meta-data/instance-id" target="_blank">http://192.168.0.2//latest/meta-data/instance-id</a>' failed [0/120s]: request error [HTTPConnectionPool(host='192.168.0.2', port=80): Max retries exceeded with url: //latest/meta-data/instance-id (Caused by <class 'socket.error'>: [Errno 111] Connection refused)]</pre>
<pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap"><br></pre><pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap"><br></pre></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
2014-06-14 20:04 GMT+03:00 Mike Spreitzer <span dir="ltr"><<a href="mailto:mspreitz@us.ibm.com" target="_blank">mspreitz@us.ibm.com</a>></span>:<div><div class="h5"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<tt><font>Sergey Motovilovets <<a href="mailto:motovilovets.sergey@gmail.com" target="_blank">motovilovets.sergey@gmail.com</a>>
wrote on 06/14/2014 11:00:09 AM:<br>
...<div><br>
> Another problem is metadata service. I've tried like everything I
<br>
> found regarding neutron<->metadata configuration, without any
<br>
> success. I just can't connect to 169.254.169.254 from virtual <br>
> machines, though they get configured by dhcp, can ping each other
in<br>
> their subnet and I can allocate floating IPs to them.</div></font></tt>
<br><tt><font>> ...</font></tt>
<br>
<br><tt><font>Did yo look to see if there is a wrong route in your
VM? Sometimes I find the metadata service is messed up by a bogus
entry in the VM's routing table.</font></tt>
<br>
<br><tt><font>Regards,</font></tt>
<br><tt><font>Mike</font></tt></blockquote></div></div></div><br></div>
</blockquote></div><br></div></div>