This is part of IBM Smart Cloud Orchestrator which is running openstack as the backend. I compared my IPtables to a working environment and it looks fine. I have rebooted and restarted. The VM's are getting a 169 route but can't ping. The only place I can ping is on the Region server which is where the 169 address sits.
Howard Luckenbaugh Special Events Infrastructure/IBM.com Infrastructure T/L-349-5884 Fax- 1877-210-0298 hluc...@us.ibm.com AIX System Certified Please visit the sites that our team hosts: http://www.ibm.com http://www.wimbledon.com http://www.usopen.org http://www.masters.com http://www.austrailianopen.com http://www.usopen.com "Vision without Action is just a dream Actions without Vision is just passing time Vision with Action can change the world" From: "Gangur, Hrushikesh (R & D HP Cloud)" <hrushikesh.gan...@hp.com> To: Robert Collins <robe...@robertcollins.net>, Howard Luckenbaugh/Raleigh/IBM@IBMUS Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org> Date: 05/11/2014 11:29 PM Subject: RE: [Openstack] nova ip 169.254.169.254 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:robe...@robertcollins.net] Sent: Saturday, May 10, 2014 3:03 PM To: Howard Luckenbaugh Cc: openstack@lists.openstack.org Subject: Re: [Openstack] nova ip 169.254.169.254 On 10 May 2014 06:16, Howard Luckenbaugh <hluc...@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 <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
