-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.16
This is a clone of issue OCPBUGS-56873. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-56865. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-48672. The following is the description of the original issue:
—
Description of problem:
avoidBuggyIPs option is added automatically to the IPAddressPool resource and this is displayed as the deviation by the cluster-compare tool 13:29:36 --- /tmp/MERGED-3723343361/metallb-io-v1beta1_ipaddresspool_metallb-system_demopool 2025-01-21 14:29:34.358466640 +0200 13:29:36 +++ /tmp/LIVE-2560493300/metallb-io-v1beta1_ipaddresspool_metallb-system_demopool 2025-01-21 14:29:34.358466640 +0200 13:29:36 @@ -11,4 +11,5 @@ 13:29:36 - fd12:4562:4563:4564::1/128 13:29:36 - autoAssign: true 13:29:36 + autoAssign: false 13:29:36 + avoidBuggyIPs: false
Version-Release number of selected component (if applicable):
OCP-4.16
How reproducible:
100%
Steps to Reproduce:
1. Deploy OCP cluster per RDS Core guidelines 2. Run cluster-compare tool 3.
Actual results:
As this option is added by the operator? it should be tolerated by the tool
Expected results:
Option should be tolerated by the tool
Additional info:
- blocks
-
OCPBUGS-57132 Tolerate avoidBuggyIPs option within IPAddressPool
-
- ON_QA
-
- clones
-
OCPBUGS-56873 Tolerate avoidBuggyIPs option within IPAddressPool
-
- ON_QA
-
- is blocked by
-
OCPBUGS-56873 Tolerate avoidBuggyIPs option within IPAddressPool
-
- ON_QA
-
- is cloned by
-
OCPBUGS-57132 Tolerate avoidBuggyIPs option within IPAddressPool
-
- ON_QA
-
- links to
- mentioned on