-
Bug
-
Resolution: Done
-
Normal
-
4.13.z, 4.12.z
Description of problem:
MetalLB is accepting BGPAdvertisements with different local preferences in 4.12 and 4.13. In consequence it is effecting route advertisement. This is not the case from 4.14 as the webhook is preventing this while creating BGPAdvertisement resource with different local preference.
Requirement is to backport the fix to 4.12 and 4.13
Version-Release number of selected component (if applicable): 4.12.60
metallb-operator.4.12.0-202406190905
How reproducible: 100%
Steps to Reproduce:
1. Create BGPAdvertisement with IPAddressPool1 with local preference 100
2. Create BGPAdvertisement with IPAddressPool1 with local preference 500 with nodeselector and bgp peer
Actual results: Both get accepted. This effects the route advertisement with both local preference advertised. Also the behaviour is not consistent when swapping step1 and step2
Expected results:
Webhook to reject bgpadvertisement when creating with different local preference.
Additional info:
YAML data
https://drive.google.com/drive/folders/1dgmf84GsMdI58219xPD-jmhEDSJ1yeuS?usp=sharing
- account is impacted by
-
OCPBUGS-32020 Localpref for different aggregation lengths is not validated correctly
- Closed
- blocks
-
OCPBUGS-41931 BGP multiple local preference checkpoint
- New
- is cloned by
-
OCPBUGS-41931 BGP multiple local preference checkpoint
- New
- links to