metadata agent): 1. Check through
> VM's console.log whe
>
> From: "Gangur, Hrushikesh (R & D HP Cloud)"
> To: Robert Collins , Howard
> Luckenbaugh/Raleigh/IBM@IBMUS
> Cc: "openstack@lists.openstack.org"
> Date: 05/11/2014 11:29 PM
> S
To: Howard Luckenbaugh/Raleigh/IBM@IBMUS
Cc: "Gangur, Hrushikesh (R & D HP Cloud)"
, "openstack@lists.openstack.org"
Date: 05/12/2014 10:27 AM
Subject:Re: [Openstack] nova ip 169.254.169.254
The VMs typically shouldn't have a
"
To: Robert Collins , Howard
Luckenbaugh/Raleigh/IBM@IBMUS
Cc: "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):
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.1
On 10 May 2014 06:16, Howard Luckenbaugh 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 happe
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.
Howard Luckenbaugh
Special Events Inf
