dhcp_agent/force_metadata not required
Bug #1872960 reported by
Fabian Zimmermann
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla-ansible |
In Progress
|
Undecided
|
Fabian Zimmermann | ||
Bug Description
https:/
introduced "force_metadata" in dhcp_agent.ini to get cloud-init working. I dont think this is a good idea, because:
1. Its not required to do this. "enable_
2. force_metadata will *always* start the metadata-api on the dhcp-agents even if a router is available.
3. If you only run one dhcp-agent per network and this agent fails, you dont have any metadata-api, but if you run l3-ha-routers in this network, your metadata-api will failover to the active node.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to kolla-ansible (master) | #1 |
| Changed in kolla-ansible: | |
| assignee: | nobody → Fabian Zimmermann (dev-faz) |
| status: | New → In Progress |
Revision history for this message
| Tom Fifield (fifieldt) wrote | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on kolla-ansible (master) | #4 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/