When isolated metadata is enabled, metadata proxy doesn't get automatically started/stopped when needed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Daniel Alvarez |
Bug Description
When enabled_
100% reproducible:
With enable_
1. Create a network, a subnet and a router.
2. Check that there's a proxy instance running in the DHCP namespace for this network:
neutron 800009 1 0 17:01 ? 00:00:00 haproxy -f /var/lib/
3. Attach the subnet to the router.
4. Verify that the proxy instance is still running.
5. Restart DHCP agent
6. Verify that the proxy instance went away (since the network is not isolated).
7. Remove the subnet from the router.
8. Verify that the proxy instance has not been spawned.
At this point, booting any VM on the network will fail since it won't be able to fetch metadata.
However, any update on the network/subnet will trigger the agent to refresh the status of the isolated metadata proxy:
For example: openstack network set <net_uuid> --name foo
would trigger that DHCP agent spawns the proxy for that network.
Changed in neutron: | |
assignee: | nobody → Daniel Alvarez (dalvarezs) |
summary: |
- When isolated/force metadata is enabled, metadata proxy doesn't get + When isolated metadata is enabled, metadata proxy doesn't get automatically started/stopped when needed |
Changed in neutron: | |
importance: | Undecided → High |
tags: | added: l3-ipam-dhcp |
tags: | added: pike-backport-potential |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
Fix proposed to branch: master /review. openstack. org/549822
Review: https:/