Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-35829

Live migration gets stuck when the ConfigMap MTU is absent

XMLWordPrintable

    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      [id="ocp-4-16-2-known-issue_{context}"]
      ==== Known issue

      * If the `ConfigMap` maximum transmission unit (MTU) is absent in the namespace 'openshift-network-operator', users have to create the `ConfigMap` manually with the machine MTU value, before starting the live migration. Otherwise, the live migration will get stuck and fail. (link:https://issues.redhat.com/browse/OCPBUGS-35829[*OCPBUGS-35829*])
      ___________
      If the configmap 'mtu' is absent in the namespace 'openshift-network-operator'. Users have to create the configmap manually with the machine MTU value, before starting the live migration.
      Show
      [id="ocp-4-16-2-known-issue_{context}"] ==== Known issue * If the `ConfigMap` maximum transmission unit (MTU) is absent in the namespace 'openshift-network-operator', users have to create the `ConfigMap` manually with the machine MTU value, before starting the live migration. Otherwise, the live migration will get stuck and fail. (link: https://issues.redhat.com/browse/OCPBUGS-35829 [* OCPBUGS-35829 *]) ___________ If the configmap 'mtu' is absent in the namespace 'openshift-network-operator'. Users have to create the configmap manually with the machine MTU value, before starting the live migration.
    • Known Issue
    • Done
    • Network

      This is a clone of issue OCPBUGS-35316. The following is the description of the original issue:
      —
      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.

              pliurh Peng Liu
              openshift-crt-jira-prow OpenShift Prow Bot
              Zhanqi Zhao Zhanqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: