Re: [Openstack-operators] [openstack operators][neutron] Neutron Router getting address not inside allocation range on provider network

Thanks, Kevin. I agree that it seems like a bug. I'll go ahead and file. Chris On March 22, 2018 05:10:08 Kevin Benton wrote: I think you might have uncovered an edge-case that should probably be filed as a bug against Neutron. If a router interface is attached using a reference to a subne

Re: [Openstack-operators] [openstack operators][neutron] Neutron Router getting address not inside allocation range on provider network

I think you might have uncovered an edge-case that should probably be filed as a bug against Neutron. If a router interface is attached using a reference to a subnet, it always tries to use the address in the "gateway_ip" of the subnet: https://github.com/openstack/neutron/blob/282d3da614f24a6385c

[Openstack-operators] [openstack operators][neutron] Neutron Router getting address not inside allocation range on provider network

All, Had a strange incident the other day that seems like it shouldn't be possible inside of neutron... We are currently running Queens on Ubuntu 16.04 w/ the linuxbridge ml2 plugin with vxlan overlays. We have a single, large provider network that we have set to 'shared' and 'external', so