This is an RFC voilation. This should be addressed by the Operating
System images rather than worked around by Neutron. There should be no
such existing routes in the image(s).
** Changed in: neutron
Assignee: Pranav Salunke (dguitarbite) => (unassigned)
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1426305
Title:
metadata server not reachable with 169.254.0.0/16 route
Status in neutron:
Invalid
Bug description:
With openvswitch (tested both vlan and gre)
metadata server is not reachable
when a 169.254.0.0/16 local route is present in a cloud VM
(as is the default with some OS versions)
Steps To Reproduce:
in a cloud VM do
ip r add 169.254.0.0/16 dev eth0
curl 169.254.169.254
Without this route, metadata traffic is routed through the default gw
and thus working fine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1426305/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
