Comment 21 for bug 1629133

I have added neutron back to this bug because it is still not fixed.

I'm going to restate the problem:

In the gate, a 'safe' network range is added to the devstack config. This is a range that, in terms of the gate, can be used for things and is known to not conflict with existing network ranges in the various gate clouds.

As part of setting itself up, neutron ignores that setting.

The reason it ignores it seems to be based in a technically valid viewpoint that FIXED_RANGE and SUBNETPOOL_PREFIX_V4 mean different things. That's fine.

What's not fine is for the solution (or lack of one) to break the networking of nodes in the gate. Especially since we just flipped the switch on neutron-by-default.

So unless there is actually a solution to OpenStack developers not being able to run jobs in the gate without broken networking, let's not call this one either fixed or not-relevant. Setting SUBNETPOOL_PREFIX_V4=$FIXED_RANGE seems fine for the gate. If it's not, let's find a solution that is.