Public bug reported:
* High level description:
When creating a static route in a l3 router where the destination subnet
already exists as connected network.
Adding the route will remove the directly connected network and add the
static route.
After removing the static route the directly connected route does not
get restated.
* Pre-conditions:
This has been tested on Ussuri, with:
- Neutron Linux bridge agent
- Neutron L3 agent
- Neutron
* Step-by-step reproduction steps:
Creating a route where the destination already exists
# openstack network create network1
# openstack subnet create --network network1 --subnet-range 192.168.1.0/24
network1-sub-1
# openstack network create network2
# openstack subnet create --network network2 --subnet-range 192.168.2.0/24
network2-sub-1
# openstack router create router1
# openstack router add subnet router1 network1-sub-1
# openstack router add subnet router1 network2-sub-1
# Add the route, this will remove the connected network and add a static route
# openstack router add route --route
destination=192.168.1.0/24,gateway=192.168.2.10 router1
# remove the static route, this will remove the route but will not add the
connected network
# openstack router remove route --route
destination=192.168.1.0/24,gateway=192.168.2.10 router1
It is also possible to create a route in the same network:
# openstack network create network1
# openstack subnet create --network network1 --subnet-range 192.168.1.0/24
network1-sub-1
# openstack router create router1
# openstack router add subnet router1 network1-sub-1
# openstack router add route --route
destination=192.168.1.0/24,gateway=192.168.1.10 router1
# openstack router remove route --route
destination=192.168.1.0/24,gateway=192.168.1.10 router1
* Expected output:
1. Or that the connected route will never get removed
2. Or that the connected route restated when the static route is removed
* Version:
** OpenStack version: Ussuri
** Ubuntu Bionic
* Environment:
* Perceived severity:
This can be a high impact when the customer add a route where the destination
has high/important traffic in that flow.
* Workaround
- Currently by disabling the router and then enabling the router will rebuild
the who router and so also the missing routes.
- Using "neutron l3-agent-router-remove" and "neutron l3-agent-router-
add" commands will also rebuilt the router
** Affects: neutron
Importance: Undecided
Status: New
** Tags: neutron neutron-l3-agent static-route
** Tags added: neutron
** Tags added: neutron-l3-agent static-route
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1954777
Title:
setting same static route with subnet already exists as direct
connected network
Status in neutron:
New
Bug description:
* High level description:
When creating a static route in a l3 router where the destination
subnet already exists as connected network.
Adding the route will remove the directly connected network and add
the static route.
After removing the static route the directly connected route does not
get restated.
* Pre-conditions:
This has been tested on Ussuri, with:
- Neutron Linux bridge agent
- Neutron L3 agent
- Neutron
* Step-by-step reproduction steps:
Creating a route where the destination already exists
# openstack network create network1
# openstack subnet create --network network1 --subnet-range 192.168.1.0/24
network1-sub-1
# openstack network create network2
# openstack subnet create --network network2 --subnet-range 192.168.2.0/24
network2-sub-1
# openstack router create router1
# openstack router add subnet router1 network1-sub-1
# openstack router add subnet router1 network2-sub-1
# Add the route, this will remove the connected network and add a static route
# openstack router add route --route
destination=192.168.1.0/24,gateway=192.168.2.10 router1
# remove the static route, this will remove the route but will not add the
connected network
# openstack router remove route --route
destination=192.168.1.0/24,gateway=192.168.2.10 router1
It is also possible to create a route in the same network:
# openstack network create network1
# openstack subnet create --network network1 --subnet-range 192.168.1.0/24
network1-sub-1
# openstack router create router1
# openstack router add subnet router1 network1-sub-1
# openstack router add route --route
destination=192.168.1.0/24,gateway=192.168.1.10 router1
# openstack router remove route --route
destination=192.168.1.0/24,gateway=192.168.1.10 router1
* Expected output:
1. Or that the connected route will never get removed
2. Or that the connected route restated when the static route is removed
* Version:
** OpenStack version: Ussuri
** Ubuntu Bionic
* Environment:
* Perceived severity:
This can be a high impact when the customer add a route where the destination
has high/important traffic in that flow.
* Workaround
- Currently by disabling the router and then enabling the router will rebuild
the who router and so also the missing routes.
- Using "neutron l3-agent-router-remove" and "neutron l3-agent-
router-add" commands will also rebuilt the router
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1954777/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
