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

Roll Back to OpenShift SDN gets stuck during the live migration method

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • None
    • None
    • Customer Escalated
    • Done
    • Bug Fix
    • Hide
      * Previously, an incomplete container network interface (CNI) redeployment caused an issue during limited live migration. This issue led to potential network connectivity problems during rollback to {product-title} software-defined networking (SDN) for users. With this release, a bug fix adds an annotation for the primary IP address of a node to handle non-cloud platforms during egress IP address rollback. The fix ensures a smooth rollback to {product-title} SDN, resolving stuck issues that occur during limited live migration, and improving network connectivity. (link:https://issues.redhat.com/browse/OCPBUGS-53317[OCPBUGS-53317])
      Show
      * Previously, an incomplete container network interface (CNI) redeployment caused an issue during limited live migration. This issue led to potential network connectivity problems during rollback to {product-title} software-defined networking (SDN) for users. With this release, a bug fix adds an annotation for the primary IP address of a node to handle non-cloud platforms during egress IP address rollback. The fix ensures a smooth rollback to {product-title} SDN, resolving stuck issues that occur during limited live migration, and improving network connectivity. (link: https://issues.redhat.com/browse/OCPBUGS-53317 [ OCPBUGS-53317 ])
    • None
    • None
    • None
    • None

      Description of problem: Rollback to OpenShift SDN gets stuck during the Limited Live Migration method

      Version-Release number of selected component (if applicable): 4.15.31

      Details:

      The migration is currently stuck after the CNI gets redeployed 

          conditions:
    - lastTransitionTime: "2025-03-17T08:06:22Z"
      message: The desired MachineConfig is not applied to cluster
      reason: MachineConfigNotApplied
      status: "False"
      type: NetworkTypeMigrationMTUReady
    - lastTransitionTime: "2025-03-17T08:06:22Z"
      message: DaemonSet ovnkube-node is not ready
      reason: TargetCNINotReady
      status: "False"
      type: NetworkTypeMigrationTargetCNIAvailable
    - lastTransitionTime: "2025-03-17T08:06:22Z"
      message: The desired MachineConfig is not applied to cluster
      reason: MachineConfigNotApplied
      status: "False"
      type: NetworkTypeMigrationTargetCNIInUse
    - lastTransitionTime: "2025-03-17T08:06:22Z"
      message: The original CNI plugin is running in the cluster
      reason: OriginalCNINotPurged
      status: "False"
      type: NetworkTypeMigrationOriginalCNIPurged
    - lastTransitionTime: "2025-03-17T08:06:22Z"
      message: Network type migration is started
      reason: NetworkTypeMigrationStarted
      status: "True"
      type: NetworkTypeMigrationInProgress

      More details in the comment section

              pliurh Peng Liu
              rhn-support-hchaturv Himank Chaturvedi
              None
              None
              Weibin Liang Weibin Liang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: