yahoo-eng-team team mailing list archive

[Armando Migliaccio <1239481@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (INCUBATOR-JUNO, LIBERTY, MITAKA, NEWTON).
  Valid example: CONFIRMED FOR: INCUBATOR-JUNO


** Changed in: neutron
       Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1239481

Title:
  nova baremetal requires manual neutron setup for metadata access

Status in Ironic:
  Confirmed
Status in neutron:
  Expired
Status in OpenStack Compute (nova):
  Won't Fix
Status in tripleo:
  Incomplete

Bug description:
  a subnet setup with host routes can use a bare metal gateway as long as there is a metadata server on the same network:
  neutron subnet-create ... (network, dhcp settings etc) ----host_routes type=dict list=true destination=169.254.169.254/32,nexthop=<nova metadata server> --gateway_ip=<actual gateway>

  But this requires manual configuration - it would be nice if nova
  could configure this as part of bringing up the network for a given
  node.

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