Public bug reported:
We are using Rocky 13.0.6 neutron which seems removing router namespace if retry limit got hit. After some investigations, it seems that delete a server which already associates with a floating ip address seems causes a broadcast notification to all related routers. In our cases, we have around 300 compute nodes and they all have l3 dvr agents running on. the related code snippet is https://github.com/openstack/neutron/blob/bb4c26eb7245465bf7cea7e0f07342601eb78ede/neutron/db/l3_db.py#L1999, so my question is: is it still relevant to have it if dvr is enabled? ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1968837 Title: too many l3 dvr agents got notifications after a server got deleted Status in neutron: New Bug description: We are using Rocky 13.0.6 neutron which seems removing router namespace if retry limit got hit. After some investigations, it seems that delete a server which already associates with a floating ip address seems causes a broadcast notification to all related routers. In our cases, we have around 300 compute nodes and they all have l3 dvr agents running on. the related code snippet is https://github.com/openstack/neutron/blob/bb4c26eb7245465bf7cea7e0f07342601eb78ede/neutron/db/l3_db.py#L1999, so my question is: is it still relevant to have it if dvr is enabled? To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1968837/+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
