Set local_ip only when TENANT_TUNNELS are enabled
In an installation with VLAN tenant networks, devstack should not configure the local_ip (which is applicable only when tenant_tunnels are used). This is causing failures in Neutron for an IPv6 only setup. This patch addresses this issue, but configuring the local_ip only when TENANT_TUNNELS are enabled. Related-Bug: #1447693 Change-Id: I0e2a2d8b6ce0ad87f6c0d318ac522dbab50d44ee
This commit is contained in:
parent
4e41fd83b6
commit
8d558c8c27
@ -104,8 +104,10 @@ function neutron_plugin_configure_service {
|
|||||||
iniset /$Q_PLUGIN_CONF_FILE securitygroup firewall_driver neutron.agent.firewall.NoopFirewallDriver
|
iniset /$Q_PLUGIN_CONF_FILE securitygroup firewall_driver neutron.agent.firewall.NoopFirewallDriver
|
||||||
fi
|
fi
|
||||||
|
|
||||||
# Since we enable the tunnel TypeDrivers, also enable a local_ip
|
if [[ "$ENABLE_TENANT_TUNNELS" == "True" ]]; then
|
||||||
iniset /$Q_PLUGIN_CONF_FILE ovs local_ip $TUNNEL_ENDPOINT_IP
|
# Set local_ip if TENANT_TUNNELS are enabled.
|
||||||
|
iniset /$Q_PLUGIN_CONF_FILE ovs local_ip $TUNNEL_ENDPOINT_IP
|
||||||
|
fi
|
||||||
|
|
||||||
populate_ml2_config /$Q_PLUGIN_CONF_FILE ml2 mechanism_drivers=$Q_ML2_PLUGIN_MECHANISM_DRIVERS
|
populate_ml2_config /$Q_PLUGIN_CONF_FILE ml2 mechanism_drivers=$Q_ML2_PLUGIN_MECHANISM_DRIVERS
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user