-
Bug
-
Resolution: Done-Errata
-
Major
-
4.16.0
-
No
-
Rejected
-
False
-
Description of problem:
CNO assumes only master and worker machine config pools present on the cluster, While running CI with 24 nodes, it's found that there are two more pools infra and workload present. So these pools are also taken into consideration while rolling out ipsec machine config.
# omg get mcp NAME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READYMACHINECOUNT UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT AGE infra rendered-infra-52f7615d8c841e7570b7ab6cbafecac8 True False False 3 3 3 0 38m master rendered-master-fbb5d8e1337d1244d30291ffe3336e45 True False False 3 3 3 0 1h10m worker rendered-worker-52f7615d8c841e7570b7ab6cbafecac8 False True False 24 12 12 0 1h10m workload rendered-workload-52f7615d8c841e7570b7ab6cbafecac8 True False False 0 0 0 0 38m
- blocks
-
SDN-4313 add e2e ipsec upgrade ci lane to prow
- Closed
-
SDN-4384 revise all prow ipsec lanes
- Closed
- is cloned by
-
OCPBUGS-37205 CNO must consider infra and workload machine config pools for IPsec rollout
- Closed
- is depended on by
-
OCPBUGS-37205 CNO must consider infra and workload machine config pools for IPsec rollout
- Closed
- is related to
-
SDN-5146 Impact: Unexpected Behavior During Cluster Upgrade (4.14.23 to 4.15.15) for the ovn-ipsec-host pods
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update