yahoo-eng-team team mailing list archive

[Michael Kerrin <michael.kerrin@xxxxxx>]

I c an confirm that this a change made after this commit to nova
7fa9b7e0cccdedb4a4fbd12ed3db1dab30cb3ddc causes the problem. The time
line from when I see internal failures matches this also.

** Also affects: nova
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1307424

Title:
  undercloud won't come up: seed metadata server 404s

Status in OpenStack Compute (Nova):
  New
Status in tripleo - openstack on openstack:
  Confirmed

Bug description:
  With a fresh update and a new deployment across the board, the
  undercloud won't boot. It has a route to 169.254.169.254, back to the
  seed IP (192.0.2.1). The nova-api metadata service is responding to
  requests to it, but attempting to fetch

  http://169.254.169.254/latest/meta-data

  return an HTTP 404.

  On the seed node, the nova-api.log is full of these:

  2014-04-14 10:21:16.346 3939 ERROR nova.api.metadata.handler [-]
  Failed to get metadata for ip: 192.0.2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1307424/+subscriptions