Browse code
Revert "turn multi host true for nova network by default"
This reverts commit 2e1a91c50b73ca7f46871d3a906ade93bbcac6a7
It looks like this introduced race bug 1491949 in the
gate-tempest-dsvm-large-ops job causing rpc timeouts when
deallocating network information for an instance,
specifically around the dnsmasq callback to release the
fixed IP that the instance was using which triggers the
disassociation between the fixed IP and the instance in the
nova database.
Change-Id: I163cdeea75e92485f241647c69aea0d7456c3258
Closes-Bug: #1491949
Matt Riedemann authored on 2015/09/04 23:15:27Showing 1 changed files
| ... | ... |
@@ -156,7 +156,7 @@ FLAT_INTERFACE=${FLAT_INTERFACE:-$GUEST_INTERFACE_DEFAULT}
|
| 156 | 156 |
# ``MULTI_HOST`` is a mode where each compute node runs its own network node. This |
| 157 | 157 |
# allows network operations and routing for a VM to occur on the server that is |
| 158 | 158 |
# running the VM - removing a SPOF and bandwidth bottleneck. |
| 159 |
-MULTI_HOST=$(trueorfalse True MULTI_HOST) |
|
| 159 |
+MULTI_HOST=$(trueorfalse False MULTI_HOST) |
|
| 160 | 160 |
|
| 161 | 161 |
# ``NOVA_ALLOW_MOVE_TO_SAME_HOST`` can be set to False in multi node DevStack, |
| 162 | 162 |
# where there are at least two nova-computes. |