Hi,

W dniu pon, 9 maj 2022 o 13:49:22 -0400 użytkownik J-P Methot <jp.methot@planethoster.info> napisał:

I tested this on my own DVR test environment with a random static route and I'm getting the same results as on production. Here's what I get in the logs :

2022-05-09 17:28:50.018 691 INFO neutron.agent.l3.agent [-] Starting processing update 41fcd10b-7db5-45d9-b23c-e22f34c45eec, action 3, priority 1, update_id 9e112de1-f538-4a41-9526-152aa3937129. Wait time elapsed: 0.001
2022-05-09 17:28:50.019 691 INFO neutron.agent.l3.agent [-] Starting router update for 41fcd10b-7db5-45d9-b23c-e22f34c45eec, action 3, priority 1, update_id 9e112de1-f538-4a41-9526-152aa3937129. Wait time elapsed: 0.002
2022-05-09 17:28:51.640 691 INFO neutron.agent.l3.agent [-] Finished a router update for 41fcd10b-7db5-45d9-b23c-e22f34c45eec, update_id 9e112de1-f538-4a41-9526-152aa3937129. Time elapsed: 1.622

As you can see, there was an attempt at updating the router and it did return as successful. However, there was no new route added in the router or floating ip namespace. No error either.

Can You do the same with debug logs enabled?

On 5/6/22 14:40, Slawek Kaplonski wrote:
Hi,

W dniu pią, 6 maj 2022 o 14:14:47 -0400 użytkownik J-P Methot <jp.methot@planethoster.info> napisał:

Hi,

We're in this situation where we are going to move some instances from one openstack cluster to another. After this process, we want our instances on the new openstack cluster to keep the same floating IPs but also to be able to communicate with some instances that are in the same public IP range on the first cluster.

To accomplish this, we want to add static routes like 'X.X.X.X/32 via Y.Y.Y.Y'. However, we're using DVR and when we add the static routes, they do not show up anywhere in any of the namespaces. Is there a different way to add static routes on DVR instead of using openstack router add route ?

No, there is no other way to add static routes to the dvr router. I don't have any DVR deployment now to check it but IIRC route should be added in the qrouter namespace in the compute nodes where router exists. If it's not there please check logs of the l3-agent on those hosts, maybe there are some errors there.
-- 
Jean-Philippe Méthot
Senior Openstack system administrator
Administrateur système Openstack sénior
PlanetHoster inc.
-- 
Slawek Kaplonski
Principal Software Engineer
Red Hat
-- 
Jean-Philippe Méthot
Senior Openstack system administrator
Administrateur système Openstack sénior
PlanetHoster inc.

-- 
Slawek Kaplonski
Principal Software Engineer
Red Hat