metadata proxy launched by l3 agent is missing the metadata port
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
mouadino | ||
Grizzly |
Fix Released
|
Medium
|
Gary Kotton |
Bug Description
While configuring quantum to run in my own setup with namespace enable and after i created 2 quantum networks and an internal router, i remarked that whenever i start a VM, this later can't connect to the metadata service.
So after digging in the namespace of the router, using the commands:
$ ip netns exec <router-id> netstat -anp
$ ip netns exec <router-id> iptables-save | grep 169.254.169.254
I saw that the quantum-
So after checking the code i saw that the iptables rule for pre-routing the package from 169.254.169.254 to the metadata quantum server port was correct but when it come to the proxy (i.e. quantum-
I am including here a patch that fix this and hopefully my conclusion was correct and that i didn't miss anything.
N.B: This is my first contribution to the OpenStack project.
tags: | added: l3-ipam-dhcp |
Changed in quantum: | |
importance: | Undecided → Medium |
Changed in quantum: | |
status: | New → Confirmed |
Changed in quantum: | |
milestone: | none → havana-1 |
tags: | added: grizzly-backport-potential |
tags: | removed: grizzly-backport-potential |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
tags: | removed: in-stable-grizzly |
Changed in neutron: | |
milestone: | havana-1 → 2013.2 |
Here the patch:
https:/ /review. openstack. org/#/c/ 25526/