-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.16.0
-
None
Description of problem:
Live migration gets stuck when the ConfigMap MTU is absent. The ConfigMap mtu should be created by the mtu-prober job at the installation time since 4.11. But if the cluster was upgrade from a very early releases, such as 4.4.4, the ConfigMap mtu may be absent.
Version-Release number of selected component (if applicable):
4.16.rc2
How reproducible:
Steps to Reproduce:
1. build a 4.16 cluster with OpenShiftSDN 2. remove the configmap mtu from the namespace cluster-network-operator. 3. start live migration.
Actual results:
Live migration gets stuck with error NetworkTypeMigrationFailed Failed to process SDN live migration (configmaps "mtu" not found)
Expected results:
Live migration finished successfully.
Additional info:
A workaround is to create the configmap mtu manually before starting live migration.
- blocks
-
OCPBUGS-35829 Live migration gets stuck when the ConfigMap MTU is absent
- Closed
- is cloned by
-
OCPBUGS-35829 Live migration gets stuck when the ConfigMap MTU is absent
- Closed
-
OCPBUGS-41821 Document that Live migration gets stuck when the ConfigMap MTU is absent in KCS
- Closed
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update