yahoo-eng-team team mailing list archive

[Alan Pevec <1160955@xxxxxxxxxxxxxxxxxx>]

** Changed in: quantum/grizzly
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1160955

Title:
  metadata proxy launched by l3 agent is missing the metadata port

Status in OpenStack Quantum (virtual network service):
  Fix Committed
Status in quantum grizzly series:
  Fix Released

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-ns-metadata-proxy process was listening on the
  wrong port, because in my case i had configured the metadata quantum
  server to listen on a different port than the default one (9697) in
  the l3_agent configuration, while the pre-routing iptables rule was
  configured correctly.

  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-
  ns-metadata-proxy), i saw that it wasn't getting the right
  configuration from anywhere and that's why it was listening on the
  default port (9697).

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1160955/+subscriptions