Comment 4 for bug 1959699

> First of all, let me pointing out that [1] was not the same problem as in this bug. In [1],
> the router port had an IP address outside the subnet CIDR; that was an error. This is not
> the case here, were the FIP receives an IP address in this range.

The bug report in [1] sais "IP address for a router interface allowed outside the allocation range of subnet". The IP address was inside the subnet CIDR, but not inside the allocation range and this was deemed to be a problem. In this case Neutron chose the gateway ip for the router, which is inside the subnet's CIDR, but outside of the subnet's allocation pool. The python test I pasted shows similar behavior; if you print the public_sub you have a gateway outside the allocation pool, which is allocatable as a FIP:

> 'gateway_ip': '11.0.0.1', 'cidr': '11.0.0.0/24', 'allocation_pools': [{'start': '11.0.0.2', 'end': '11.0.0.254'}]

So, what Brian describes would solve my problem if this behavior would be implemented in OpenStack. Implementing it would probably mean writing extra validation checks for create_floatingip() with user-specified floating_ip_address.