l3-agent should nat metadata requests even if no gateway exists
Bug #1051842 reported by
dan wendlandt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
dan wendlandt |
Bug Description
Currently, the l3-agent only pushes down some of the DNAT rules for metadata mapping if there is a gateway set on a router.
The original thinking for this was that the nova API server would only be reachable via the external network. However, the nova-api server could itself be running in the local router namespace (or on the same box as the quantum-l3-agent in the case were namespaces are disabled. In face, with namespaces disabled, this is the likely setup for a simple environment).
Thus, we should simply always push down the metadata nat rules for a router, router than waiting until a gateway is added.
tags: | added: folsom-rc-potential |
Changed in quantum: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → dan wendlandt (danwent) |
tags: | removed: folsom-rc-potential |
Changed in quantum: | |
milestone: | none → folsom-rc2 |
Changed in quantum: | |
milestone: | folsom-rc2 → 2012.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/13096
Review: https:/