Comment 3 for bug 1335023

The reason I made Neutron enforce the 'gateway in subnet' rule the patch in comment 1 is that our agents don't actually support that operation, and the server/API layer didn't state as such. So you could configure a gateway out of the subnet, and just as this bug complains, the server happily accepted it but the agent failed to make the configuration.

However, it's quite easy to fix this issue in the agents. Just add a route to the gateway subnet before adding the gateway route, and there you go.

I think that a patch that fixes the issue in the agents can then change the default value for force_gateway_on_subnet back to False.