[neutron] [kolla] Static routes added to subnets after upgrading from Queens to Train
haleyb.dev at gmail.com
Wed Mar 30 17:46:18 UTC 2022
On 3/29/22 17:04, Albert Braden wrote:
> After upgrading our kolla-ansible clusters from Queens to Train, we are seeing static routes when we create subnets. We didn’t see this in Queens. For example, in our de6 region we have a network called “trust” with 3 subnets:
> Subnet CIDR Gateway
> trust-az1: 10.52.160.0/22 10.52.160.1
> trust-az2: 10.52.164.0/22 10.52.164.1
> trust-az3: 10.52.168.0/22 10.52.168.1
> Each of these subnets has 2 entries under “host_routes:” that point to the other two subnets. For example, subnet trust-az1 has these two routes:
> host_routes | destination='10.52.164.0/22', gateway='10.52.160.1' |
> | | destination='10.52.168.0/22', gateway='10.52.160.1' |
> How can we prevent these host routes from being created in Train? Do we need to change something in our config?
From the neutron side of things, host_routes of a subnet is not
automatically calculated and filled-in, they have to be manually added.
So perhaps this is something kolla is doing? At least on my Yoga setup
it is completely blank using 'openstack subnet create ...' even with
multiple subnets on a network.
How exactly are the subnets getting created?
More information about the openstack-discuss