Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionFederico Paolinelli
2023-06-16 15:20:13 UTC
Description of problem:
When creating a configuration with multiple prefix lists, without specifying the seq number and we load the file with the frr-reload.py script, the prefix lists are duplicated. We don't have a case but this was noted by a user.
Version-Release number of selected component (if applicable):
frr-7.5-4.el8_4.2.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Start with an empty frr.conf, then load
og file /etc/frr/frr.log informational
log timestamp precision 3
hostname kind-worker2
ip nht resolve-via-default
ipv6 nht resolve-via-default
route-map 172.18.0.5-in deny 20
ip prefix-list 172.18.0.5-pl-ipv4 permit 192.168.10.1/32
ip prefix-list 172.18.0.5-pl-ipv4 permit 192.168.10.3/32
ip prefix-list 172.18.0.5-pl-ipv4 permit 192.168.10.0/32
ip prefix-list 172.18.0.5-pl-ipv4 permit 192.168.10.2/32
ip prefix-list 172.18.0.5-pl-ipv4 deny any
ipv6 prefix-list 172.18.0.5-pl-ipv4 deny any
route-map 172.18.0.5-out permit 7
match ip address prefix-list 172.18.0.5-pl-ipv4
route-map 172.18.0.5-out permit 8
match ipv6 address prefix-list 172.18.0.5-pl-ipv4
route-map 172.18.0.6-in deny 20
ip prefix-list 172.18.0.6-pl-ipv4 permit 192.168.10.1/32
ip prefix-list 172.18.0.6-pl-ipv4 permit 192.168.10.3/32
ip prefix-list 172.18.0.6-pl-ipv4 permit 192.168.10.0/32
ip prefix-list 172.18.0.6-pl-ipv4 permit 192.168.10.2/32
ip prefix-list 172.18.0.6-pl-ipv4 deny any
ipv6 prefix-list 172.18.0.6-pl-ipv4 deny any
route-map 172.18.0.6-out permit 7
match ip address prefix-list 172.18.0.6-pl-ipv4
route-map 172.18.0.6-out permit 8
match ipv6 address prefix-list 172.18.0.6-pl-ipv4
router bgp 64512
no bgp ebgp-requires-policy
no bgp network import-check
no bgp default ipv4-unicast
neighbor 172.18.0.5 remote-as 64512
neighbor 172.18.0.5 port 179
neighbor 172.18.0.5 timers 30 90
neighbor 172.18.0.6 remote-as 64512
neighbor 172.18.0.6 port 179
neighbor 172.18.0.6 timers 30 90
address-family ipv4 unicast
neighbor 172.18.0.5 activate
neighbor 172.18.0.5 route-map 172.18.0.5-in in
neighbor 172.18.0.5 route-map 172.18.0.5-out out
exit-address-family
address-family ipv6 unicast
neighbor 172.18.0.5 activate
neighbor 172.18.0.5 route-map 172.18.0.5-in in
neighbor 172.18.0.5 route-map 172.18.0.5-out out
exit-address-family
address-family ipv4 unicast
neighbor 172.18.0.6 activate
neighbor 172.18.0.6 route-map 172.18.0.6-in in
neighbor 172.18.0.6 route-map 172.18.0.6-out out
exit-address-family
address-family ipv6 unicast
neighbor 172.18.0.6 activate
neighbor 172.18.0.6 route-map 172.18.0.6-in in
neighbor 172.18.0.6 route-map 172.18.0.6-out out
exit-address-family
address-family ipv4 unicast
network 192.168.10.0/32
network 192.168.10.1/32
network 192.168.10.2/32
network 192.168.10.3/32
exit-address-family
2.
3.
Actual results:
3 occurrences of each prefix list, when running vtysh show running-conf
ip prefix-list 172.18.0.5-pl-ipv4 seq 5 permit 192.168.10.1/32
ip prefix-list 172.18.0.5-pl-ipv4 seq 10 permit 192.168.10.3/32
ip prefix-list 172.18.0.5-pl-ipv4 seq 15 permit 192.168.10.0/32
ip prefix-list 172.18.0.5-pl-ipv4 seq 20 permit 192.168.10.2/32
ip prefix-list 172.18.0.5-pl-ipv4 seq 25 deny any
ip prefix-list 172.18.0.5-pl-ipv4 seq 30 permit 192.168.10.1/32
ip prefix-list 172.18.0.5-pl-ipv4 seq 35 permit 192.168.10.3/32
ip prefix-list 172.18.0.5-pl-ipv4 seq 40 permit 192.168.10.0/32
ip prefix-list 172.18.0.5-pl-ipv4 seq 45 permit 192.168.10.2/32
ip prefix-list 172.18.0.5-pl-ipv4 seq 50 deny any
ip prefix-list 172.18.0.5-pl-ipv4 seq 55 permit 192.168.10.1/32
ip prefix-list 172.18.0.5-pl-ipv4 seq 60 permit 192.168.10.3/32
ip prefix-list 172.18.0.5-pl-ipv4 seq 65 permit 192.168.10.0/32
ip prefix-list 172.18.0.5-pl-ipv4 seq 70 permit 192.168.10.2/32
ip prefix-list 172.18.0.5-pl-ipv4 seq 75 deny any
Expected results:
Only one occurrency per entry
Additional info:
Hi Federico,
I see this happening on older RHEL8s, the frr-7.5.1 that is available from RHEL-8.7.0 is not affected (I did not yet find an actual commit that would tell me that this was fixed but the behavior is ok on later RHEL8s). Do you have access to newer FRR or is OCP not going to have any more rebases in RHEL8?
Regards,
Michal
Comment 2Federico Paolinelli
2023-06-28 10:18:26 UTC
Comment 5RHEL Program Management
2023-09-21 18:59:39 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 6RHEL Program Management
2023-09-21 19:45:35 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.
Description of problem: When creating a configuration with multiple prefix lists, without specifying the seq number and we load the file with the frr-reload.py script, the prefix lists are duplicated. We don't have a case but this was noted by a user. Version-Release number of selected component (if applicable): frr-7.5-4.el8_4.2.x86_64 How reproducible: Always Steps to Reproduce: 1. Start with an empty frr.conf, then load og file /etc/frr/frr.log informational log timestamp precision 3 hostname kind-worker2 ip nht resolve-via-default ipv6 nht resolve-via-default route-map 172.18.0.5-in deny 20 ip prefix-list 172.18.0.5-pl-ipv4 permit 192.168.10.1/32 ip prefix-list 172.18.0.5-pl-ipv4 permit 192.168.10.3/32 ip prefix-list 172.18.0.5-pl-ipv4 permit 192.168.10.0/32 ip prefix-list 172.18.0.5-pl-ipv4 permit 192.168.10.2/32 ip prefix-list 172.18.0.5-pl-ipv4 deny any ipv6 prefix-list 172.18.0.5-pl-ipv4 deny any route-map 172.18.0.5-out permit 7 match ip address prefix-list 172.18.0.5-pl-ipv4 route-map 172.18.0.5-out permit 8 match ipv6 address prefix-list 172.18.0.5-pl-ipv4 route-map 172.18.0.6-in deny 20 ip prefix-list 172.18.0.6-pl-ipv4 permit 192.168.10.1/32 ip prefix-list 172.18.0.6-pl-ipv4 permit 192.168.10.3/32 ip prefix-list 172.18.0.6-pl-ipv4 permit 192.168.10.0/32 ip prefix-list 172.18.0.6-pl-ipv4 permit 192.168.10.2/32 ip prefix-list 172.18.0.6-pl-ipv4 deny any ipv6 prefix-list 172.18.0.6-pl-ipv4 deny any route-map 172.18.0.6-out permit 7 match ip address prefix-list 172.18.0.6-pl-ipv4 route-map 172.18.0.6-out permit 8 match ipv6 address prefix-list 172.18.0.6-pl-ipv4 router bgp 64512 no bgp ebgp-requires-policy no bgp network import-check no bgp default ipv4-unicast neighbor 172.18.0.5 remote-as 64512 neighbor 172.18.0.5 port 179 neighbor 172.18.0.5 timers 30 90 neighbor 172.18.0.6 remote-as 64512 neighbor 172.18.0.6 port 179 neighbor 172.18.0.6 timers 30 90 address-family ipv4 unicast neighbor 172.18.0.5 activate neighbor 172.18.0.5 route-map 172.18.0.5-in in neighbor 172.18.0.5 route-map 172.18.0.5-out out exit-address-family address-family ipv6 unicast neighbor 172.18.0.5 activate neighbor 172.18.0.5 route-map 172.18.0.5-in in neighbor 172.18.0.5 route-map 172.18.0.5-out out exit-address-family address-family ipv4 unicast neighbor 172.18.0.6 activate neighbor 172.18.0.6 route-map 172.18.0.6-in in neighbor 172.18.0.6 route-map 172.18.0.6-out out exit-address-family address-family ipv6 unicast neighbor 172.18.0.6 activate neighbor 172.18.0.6 route-map 172.18.0.6-in in neighbor 172.18.0.6 route-map 172.18.0.6-out out exit-address-family address-family ipv4 unicast network 192.168.10.0/32 network 192.168.10.1/32 network 192.168.10.2/32 network 192.168.10.3/32 exit-address-family 2. 3. Actual results: 3 occurrences of each prefix list, when running vtysh show running-conf ip prefix-list 172.18.0.5-pl-ipv4 seq 5 permit 192.168.10.1/32 ip prefix-list 172.18.0.5-pl-ipv4 seq 10 permit 192.168.10.3/32 ip prefix-list 172.18.0.5-pl-ipv4 seq 15 permit 192.168.10.0/32 ip prefix-list 172.18.0.5-pl-ipv4 seq 20 permit 192.168.10.2/32 ip prefix-list 172.18.0.5-pl-ipv4 seq 25 deny any ip prefix-list 172.18.0.5-pl-ipv4 seq 30 permit 192.168.10.1/32 ip prefix-list 172.18.0.5-pl-ipv4 seq 35 permit 192.168.10.3/32 ip prefix-list 172.18.0.5-pl-ipv4 seq 40 permit 192.168.10.0/32 ip prefix-list 172.18.0.5-pl-ipv4 seq 45 permit 192.168.10.2/32 ip prefix-list 172.18.0.5-pl-ipv4 seq 50 deny any ip prefix-list 172.18.0.5-pl-ipv4 seq 55 permit 192.168.10.1/32 ip prefix-list 172.18.0.5-pl-ipv4 seq 60 permit 192.168.10.3/32 ip prefix-list 172.18.0.5-pl-ipv4 seq 65 permit 192.168.10.0/32 ip prefix-list 172.18.0.5-pl-ipv4 seq 70 permit 192.168.10.2/32 ip prefix-list 172.18.0.5-pl-ipv4 seq 75 deny any Expected results: Only one occurrency per entry Additional info: