Comment 9 for bug 1757482

I tested this seems like need to address another issue as comment 3 mentioned,
i created another subnet on public net with allocation_pools | {"start": "10.50.20.0", "end": "10.50.255.100"}

then I was able to create port with fixed ip that was out of pool range.
it allowed to add that port to router interface.

I guess it shouldn't have let me create an port with ip out of pool range in first place, if I am correct.
this happens only for provider subnet. below is paste of all the command I ran and output.

http://paste.openstack.org/show/722991/