-
Bug
-
Resolution: Done-Errata
-
Major
-
4.13.z
-
No
-
Rejected
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
While upgrading a loaded 250 node ROSA cluster from 4.13.13 to 4.14.rc2 the cluster failed to upgrade and was stuck at when network operator was trying
to upgrade.
Around 20 multus pods were in CrashLookpack state with the log
oc logs multus-4px8t 2023-10-10T00:54:34+00:00 [cnibincopy] Successfully copied files in /usr/src/multus-cni/rhel9/bin/ to /host/opt/cni/bin/upgrade_6dcb644a-4164-42a5-8f1e-4ae2c04dc315 2023-10-10T00:54:34+00:00 [cnibincopy] Successfully moved files in /host/opt/cni/bin/upgrade_6dcb644a-4164-42a5-8f1e-4ae2c04dc315 to /host/opt/cni/bin/ 2023-10-10T00:54:34Z [verbose] multus-daemon started 2023-10-10T00:54:34Z [verbose] Readiness Indicator file check 2023-10-10T00:55:19Z [error] have you checked that your default network is ready? still waiting for readinessindicatorfile @ /host/run/multus/cni/net.d/10-ovn-kubernetes.conf. pollimmediate error: timed out waiting for the condition
- depends on
-
OCPBUGS-20336 Upgrade from 4.13.13 to 4.14rc2 failed at 250 nodes.
- Closed
- is depended on by
-
OCPBUGS-29231 Upgrade from 4.13.13 to 4.14rc2 failed at 250 nodes.
- Closed
- links to
-
RHSA-2023:7198 OpenShift Container Platform 4.15 security update