Quantum server starts before provider network config is written
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cisco Openstack |
Confirmed
|
Undecided
|
Unassigned | ||
Folsom |
Fix Committed
|
Medium
|
Unassigned |
Bug Description
From Ian:
Quantum: I'm setting up a provider network and there's every indication that the quantum server is being started before the configuration for the provider network (network_
Changed in openstack-cisco: | |
status: | New → Confirmed |
Edgar notes a workaround:
I submitted a simple patch for this, basically restarting quantum server every time there is a change on the config files. /github. com/CiscoSystem s/puppet- quantum/ pull/5
https:/
To which Ian replies:
That fix is wrong, but it probably serves the purpose for now. We're missing dependencies; rather than put them in you're just restarting Quantum a lot. The problem with this is you're probably restarting Quantum several times over when the background puppet process runs every 30 minutes or so.