Fixed intermittent quantum deploy failure [1/1]

Merging in fix for DE1404: Intermittent Quantum deploy failure
from mesa

I ran into a situation where quantum failed to deploy with an exception that said that it couldn't create the fixed network because VLAN ID 1 was already taken.

Investigation showed this was because on the 1st chef client run, it failed to create the fixed network, and then created the floating network. When it created the floating network, it automatically allocated VLAN ID 1 to floating because we didn't specify one.
 On the next chef-client run, it tried to create the fixed network and failed because we have the fixed network hardcoded to VLAN ID 1.

The fix is to hard code the floating network to VLAN ID 2, which is what it will be assigned in the event of a perfect run with no errors.


 .../cookbooks/quantum/recipes/post_install_conf.rb |    1 +
 1 file changed, 1 insertion(+)

Crowbar-Pull-ID: 0f5660c71ea23328d348eef0453ed3c3a1849271

Crowbar-Release: pebbles