Description of problem: The metallb api allows to specify the community / local pref belonging to a given pool. It also allows to specify multiple communities. With the current version, all the communities are squashed and only the last one wins, and they are associated to all the ips regardless of the pool the ip belongs to. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create two addresspool, one with multiple communities, one without 2. Create two services, pinning the loadbalancer ip to the first address pool and to the second 3. Peer metallb with external bgp peers Actual results: Only one community is associated to the route (instead of two) The community is associated to both the routes (instead of only hte one related to the pool with communities defined). Same goes for local preference. Expected results: Additional info:
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