Bug 2047238 - When using communities and localpreferences together, only localpreference gets applied
Summary: When using communities and localpreferences together, only localpreference ge...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.10.0
Assignee: Federico Paolinelli
QA Contact: Greg Kopels
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-27 12:46 UTC by Federico Paolinelli
Modified: 2022-03-10 16:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:42:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift metallb pull 30 0 None open Bug 2047238: FRR route-rules: add on-match next (#1201) 2022-01-28 08:42:05 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:43:04 UTC

Description Federico Paolinelli 2022-01-27 12:46:19 UTC
Description of problem:


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


How reproducible:
Always

Steps to Reproduce:
1. Use a bgp advertisement with both communities and localpref
2.
3.

Actual results:

Only local pref gets propagated


Expected results:

Both the community and the local pref are associated with the prefix

Additional info:

Comment 4 Greg Kopels 2022-02-10 14:55:39 UTC
Bz bug validation by QE

Both Local Preference and the communities are advertised, however in the show ip bgp 10.46.56.133 (propagated route)
I only see one community 7003:007. Is this expected behavior or is my first community 65535:65282 out of range?


Cluster version is 4.10.0-fc.2

1. Create AddressPool with two communities

apiVersion: metallb.io/v1beta1
kind: AddressPool
metadata:
  name: apmaster
  namespace: metallb-system
spec:
  protocol: bgp
  autoAssign: true
  addresses:
    - 10.46.56.133-10.46.56.134
    - 2620:52:0:2e38::500-2620:52:0:2e38::600
  bgpAdvertisements:
  - communities:
    - 65535:65282
    - 7003:007
    aggregationLength: 32
    aggregationLengthV6: 128
    localPref: 400

2. Verify BGP adjacency

Neighbor        V         AS   MsgRcvd   MsgSent   TblVer  InQ OutQ  Up/Down State/PfxRcd   PfxSnt Desc
10.46.56.13     4      64500        39        34        0    0    0 00:15:53            1        0 N/A
10.46.56.14     4      64500        39        34        0    0    0 00:15:53            1        0 N/A

3. Show IP route bgp

B>* 10.46.56.133/32 [200/0] via 10.46.56.13, br-ex, weight 1, 00:09:00
  *                         via 10.46.56.14, br-ex, weight 1, 00:09:00

4. Show ip bgp 10.46.56.133

BGP routing table entry for 10.46.56.133/32, version 1
Paths: (2 available, best #2, table default, not advertised to any peer)
  Not advertised to any peer
  Local
    10.46.56.13 from 10.46.56.13 (10.131.0.2)
      Origin IGP, metric 0, localpref 400, valid, internal, multipath
      Community: 7003:7 no-advertise
      Last update: Thu Feb 10 07:25:55 2022
  Local
    10.46.56.14 from 10.46.56.14 (10.128.2.2)
      Origin IGP, metric 0, localpref 400, valid, internal, multipath, best (Router ID)
      Community: 7003:7 no-advertise
        Last update: Thu Feb 10 07:25:55 2022

5. Show ip bgp community specifying AA:NN

hlxcl7-master-0.hlxcl7.lab.eng.tlv2.redhat.com# sh ip bgp community 65535:65282
BGP table version is 1, local router ID is 10.10.10.10, vrf id 0
Default local pref 100, local AS 64500
Status codes:  s suppressed, d damped, h history, * valid, > best, = multipath,
               i internal, r RIB-failure, S Stale, R Removed
Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self
Origin codes:  i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found

   Network          Next Hop            Metric LocPrf Weight Path
*=i10.46.56.133/32  10.46.56.13              0    400      0 i
*>i                 10.46.56.14              0    400      0 i

Displayed  1 routes and 2 total paths

Comment 7 Greg Kopels 2022-02-23 05:01:30 UTC
Valdiated by QE
hlxcl7-master-0.hlxcl7.lab.eng.tlv2.redhat.com# sh ip bgp 4.4.1.10/32
BGP routing table entry for 4.4.1.10/32, version 1
Paths: (2 available, best #1, table default, not advertised to any peer)
  Not advertised to any peer
  Local
    10.46.56.14 from 10.46.56.14 (10.128.2.2)
      Origin IGP, metric 0, localpref 200, valid, internal, multipath, best (Router ID)
      Community: 7003:7 no-advertise
      Last update: Wed Feb 23 04:47:07 2022
  Local
    10.46.56.13 from 10.46.56.13 (10.131.0.2)
      Origin IGP, metric 0, localpref 200, valid, internal, multipath
      Community: 7003:7 no-advertise
      Last update: Wed Feb 23 04:47:07 2022

Comment 9 errata-xmlrpc 2022-03-10 16:42:52 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056


Note You need to log in before you can comment on or make changes to this bug.