This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2185804 - Routes are not refreshed after changing the inbound route rules from deny to permit
Summary: Routes are not refreshed after changing the inbound route rules from deny to ...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: frr
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Ruprich
QA Contact: František Hrdina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-11 09:28 UTC by Federico Paolinelli
Modified: 2023-09-21 19:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-21 19:06:12 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-6583 0 None Migrated None 2023-09-21 19:06:06 UTC
Red Hat Issue Tracker RHELPLAN-154359 0 None None None 2023-04-11 09:30:34 UTC

Description Federico Paolinelli 2023-04-11 09:28:13 UTC 
Description of problem:
A metallb configuration always have a deny all route rule to avoid external routers to be able to inject routes to the ocp nodes.

In some particular scenarios, we allow injecting a rule that overrides that in the final part of the configuration.

So, in the configuration we have something like 

route-map 172.18.0.5-in deny 20

Then we update the configuration file appending
route-map 172.18.0.5-in permit 20

and we reload it with the frr-reload.py script.


The current-config shows the rule being updated correctly, but a refresh route message is not sent to the neighbor, so any published route is not received.

This is different from what is observed with frr 8.4.2, where as soon as we update the configuration file a route refresh message is sent out

023/04/11 09:14:40.021 BGP: [WNMVF-B11FV] Processing route_map 172.30.0.2-in(IPv4:unicast) update on peer 172.30.0.2 (inbound, route-refresh)                                                                                                                
2023/04/11 09:14:40.021 BGP: [QCZ1W-VKS36] 172.30.0.2(14513de9912d) sending REFRESH_REQ for afi/safi: IPv4/unicast                                                                                                                                            
2023/04/11 09:14:40.021 BGP: [WNMVF-B11FV] Processing route_map 172.30.0.2-in(IPv6:unicast) update on peer 172.30.0.2 (inbound, route-refresh)                                                                                                                
2023/04/11 09:14:40.021 BGP: [QCZ1W-VKS36] 172.30.0.2(14513de9912d) sending REFRESH_REQ for afi/safi: IPv6/unicast 



Version-Release number of selected component (if applicable):
7.5.1

How reproducible:
Always

Steps to Reproduce:
Described above.
- A neighbor configured to push routes
- an initial config with a deny all route rule
- a new config with a permit any to amend the previous deny

Actual results:

We must either kill the session or restart the frr instance to see the routes

Expected results:

The local frr instance asks for routes to the neighbor

Additional info:
Comment 13 RHEL Program Management 2023-09-21 18:52:06 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 14 RHEL Program Management 2023-09-21 19:06:12 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.