Open Stack

Few troubleshooting steps (assuming neutron's metadata agent):
1. Check through VM's console.log whether VMs are acquiring DHCP Ip address
2. If not, check all the bridges (on both controller and compute) up and running s (br-int or br-tun), generally on reboot some of these bridges do not come up. 
3. If yes to #1, restart neutron-metadata-agent

Regards~hrushi
-----Original Message-----
From: Robert Collins [mailto:robertc at robertcollins.net] 
Sent: Saturday, May 10, 2014 3:03 PM
To: Howard Luckenbaugh
Cc: openstack at lists.openstack.org
Subject: Re: [Openstack] nova ip 169.254.169.254

On 10 May 2014 06:16, Howard Luckenbaugh <hlucken at us.ibm.com> wrote:
> This box was working and listening on 169.254.169.254 to access the 
> metadata of the machines. However it has stopped listening. I have 
> tried rebooting and comparing networks and etc and nothing I can see 
> is stopping it.  Anyone had this happen before.

If you are using neutron's nova metadata agent, it runs a process per network, then uses a domain socket to escape the network namespace and communicate with a parent that talks to nova.

If you are using nova-networking, its handled by an iptables DNAT rule to take incoming requests and forward them to the actual API IP address/port.

-Rob

--
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack at lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack