Bug 2166197

Summary: max_l3_agents_per_router=1 is ignored when an FIP is added to the instance.
Product: Red Hat OpenStack Reporter: Keigo Noha <knoha>
Component: openstack-neutronAssignee: Rodolfo Alonso <ralonsoh>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.2 (Train)CC: chrisw, froyo, ralonsoh, scohen
Target Milestone: z5Keywords: Triaged
Target Release: 16.2 (Train on RHEL 8.4)   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-neutron-15.3.5-2.20230216175502.c3c7146.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-04-26 12:17:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Keigo Noha 2023-02-01 06:21:44 UTC 
Description of problem:
max_l3_agents_per_router is ignored when FIP is added to the instance.

The details are below:
A router is created with with max_l3_agents_per_router=3.
To avoid the VRRP issue in OSP16.1.7, a user changed to   max_l3_agents_per_router=1 and remove the standby l3-agents from the router.
However, adding an FIP to an instance triggers router sync then one standby router is created.

Version-Release number of selected component (if applicable):
OSP16.2.4

How reproducible:
Every time when add an FIP to an instance.

Steps to Reproduce:
0. Create a private network and external network
1. Create a router which bridges a private network and external network with max_l3_agents_per_router=3.
2. Update max_l3_agents_per_router=1 in neutron.conf via tripleo.
3. Remove standby router from l3 agents by neutron command
4. Create an FIP and bind it to an instance in the private network.
5. Check the number of l3-agents for the router

Actual results:
At the step5, one standby router is created.

Expected results:
At the step5, no standby router is created.

Additional info:
Comment 1 Keigo Noha 2023-02-01 06:22:13 UTC 
The issue initially reported with OSP16.1.7 but the issue still persists on OSP16.2.4.
Comment 18 errata-xmlrpc 2023-04-26 12:17:48 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenStack Platform 16.2.5 (Train) bug fix and enhancement advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:1763