[Yahoo-eng-team] [Bug 1239481] Re: nova baremetal requires manual neutron setup for metadata access

2017-07-05 Thread Emilien Macchi
This bug was last updated over 180 days ago, as tripleo is a fast moving project and we'd like to get the tracker down to currently actionable bugs, this is getting marked as Invalid. If the issue still exists, please feel free to reopen it. ** Changed in: tripleo Status: Incomplete =>

[Yahoo-eng-team] [Bug 1239481] Re: nova baremetal requires manual neutron setup for metadata access

2016-09-14 Thread Jim Rollenhagen
While this is an ironic-specific problem, I don't believe the fix here is in ironic. Seems that Neutron and/or ML2 mechanisms need to set a proper route for this in the physical switch, but I'm not sure which layer that would be in. (I assume usually the agent on the host does it) ** Changed in:

[Yahoo-eng-team] [Bug 1239481] Re: nova baremetal requires manual neutron setup for metadata access

2016-08-17 Thread Armando Migliaccio
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

[Yahoo-eng-team] [Bug 1239481] Re: nova baremetal requires manual neutron setup for metadata access

2014-09-24 Thread Bruce Thompson
** Also affects: neutron Importance: Undecided Status: New -- 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

[Yahoo-eng-team] [Bug 1239481] Re: nova baremetal requires manual neutron setup for metadata access

2014-07-10 Thread Joe Gordon
Since we are in the process of deprecating nova maremetal, we should focus work on ironic instead. ** Also affects: ironic Importance: Undecided Status: New ** Changed in: nova Status: Triaged = Opinion -- You received this bug notification because you are a member of Yahoo!