Host route to metadata server is not propagated to VM with Big Switch/Floodlight plugin
Bug #1134043 reported by
Sumit Naiksatam
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Sumit Naiksatam |
Bug Description
The reason seems to be that the update to the subnet (with the host route information) is not being picked up by the dhcp agent.
Changed in quantum: | |
importance: | Undecided → High |
status: | New → In Progress |
assignee: | nobody → Sumit Naiksatam (snaiksat) |
milestone: | none → grizzly-rc1 |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | grizzly-rc1 → 2013.1 |
To post a comment you must log in.
Sumit, are you trying to inject a metadata host route via the Quantum API?
Something like:
dest 169.254.169.254/32
nexthop <ip of dhcp agent>
In that case the dhcp agent now has 'native' support for this via the 'enable_ isolated_ metadata' option.
Also the dhcp agent also allows for routed access to the metadata server even without the l3 agent.
Would that solve your problem?