frr config is not compatible with 8.0

Bug #1939332 reported by Michele Baldessari
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Incomplete
Medium
Michele Baldessari

Bug Description

While testing frr, it seems that one of our ACLs is not accepted by frr 8.0:
2021/08/09 14:18:23 BGP: [JMR52-70SM0][EC 100663332] error processing configuration change: error [validation] event [validate] operation [modify] xpath [/frr-filter:lib/prefix-list[type='ipv4'][name='only-default-host-prefixes']/entry[sequence='5']/ipv4-prefix] message: duplicated prefix list value: 0.0.0.0/0

This is because ip prefix-list only-default-host-prefixes permit 0.0.0.0/0 seems to not be parsed by frr 8.0 any longer. Potentially due to https://github.com/FRRouting/frr/commit/bf79e923167c79b2e813b7e7efda7211949d6378

While we think this is an frr bug (our frr version config is explicitly set to 7.0) and we'll chase upstream on this, let's make this config compatible with both frr versions.

tags: added: wallaby-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-ansible (master)
Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-ansible (master)

Change abandoned by "Michele Baldessari <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/tripleo-ansible/+/803972
Reason: frr upstream recognized the bug and has a fix lined up which we tested, let's just drop this

Changed in tripleo:
status: In Progress → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.