Quantum server starts before provider network config is written

[Mark T. Voelker]

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_vlan_ranges) is written. When I tried to debug a 'no provider network' error I was seeing I discovered that restarting the quantum server is enough to make it all go away. (Horizon is starting before *installation* is complete, which is just as annoying; it's probably a load of notify/subscribe required on the config files and services.) Dependencies matter, and are the cause of pretty much all of our intermittent failures; if you're writing puppet and you don't understand dependencies properly, please get someone to review your work.

[Mark T. Voelker (mvoelker)]

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.
https://github.com/CiscoSystems/puppet-quantum/pull/5

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.

[Ian Wells (ijw-ubuntu)]

Filed a new bug more specifically about puppet apply on a configured system being a no-op, which will catch the problem that Edgar's fix might be causing. Let's accept this and fix that separately in an appropriate timeframe.