quantum-netns-cleanup does not stop metadata proxies
Bug #1115999 reported by
Isaku Yamahata
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Unassigned |
Bug Description
The quantum-
affects: | devstack → quantum |
tags: | added: l3-ipam-dhcp |
summary: |
- quantum-ns-metadata-proxy remains after stopping quantum + quantum-netns-cleanup does not stop metadata proxies |
description: | updated |
Changed in quantum: | |
status: | New → Confirmed |
assignee: | nobody → Mark McClain (markmcclain) |
importance: | Undecided → High |
Changed in quantum: | |
importance: | High → Medium |
Changed in quantum: | |
milestone: | grizzly-rc1 → havana-1 |
Changed in neutron: | |
status: | In Progress → New |
To post a comment you must log in.
I seem to remember Mark McClain indicating that the behaviour in question was by design. Just as stopping the l3 agent (intentionally or no) doesn't revert iptables entries or the routing table, the proxy should probably continue running to ensure VM connectivity to the metadata service. I'm adding Mark as a bug subscriber to get his feedback.