This removes the logic to add a route pointing to the IPv4
tenant private network range since the router is performing
SNAT. If reaching the IPs via the route worked at all, it was
by accident since this behavior is certainly not guaranteed
by Neutron.
Change-Id: If45e3fc15c050cfbac11b57c1eaf137dd7ed816f
| ... | ... |
@@ -373,11 +373,6 @@ function _neutron_configure_router_v4 {
|
| 373 | 373 |
fi |
| 374 | 374 |
ROUTER_GW_IP=$(neutron --os-cloud devstack-admin --os-region "$REGION_NAME" port-list -c fixed_ips -c device_owner | grep router_gateway | awk -F'ip_address' '{ print $2 }' | cut -f3 -d\" | tr '\n' ' ')
|
| 375 | 375 |
die_if_not_set $LINENO ROUTER_GW_IP "Failure retrieving ROUTER_GW_IP" |
| 376 |
- local replace_range=${SUBNETPOOL_PREFIX_V4}
|
|
| 377 |
- if [[ -z "${SUBNETPOOL_V4_ID}" ]]; then
|
|
| 378 |
- replace_range=${FIXED_RANGE}
|
|
| 379 |
- fi |
|
| 380 |
- sudo ip route replace $replace_range via $ROUTER_GW_IP |
|
| 381 | 376 |
fi |
| 382 | 377 |
_neutron_set_router_id |
| 383 | 378 |
fi |