Bug 1989837

Summary: [Migration] SDN migration rollback failed, stuck in MCO
Product: OpenShift Container Platform Reporter: huirwang
Component: NetworkingAssignee: Peng Liu <pliu>
Networking sub component: openshift-sdn QA Contact: huirwang
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: astoycos, pliu
Version: 4.9   
Target Milestone: ---   
Target Release: 4.9.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-18 17:44:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description huirwang 2021-08-04 07:25:18 UTC
Description of problem:
SDN migration rollback failed, stuck in MCO

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

How reproducible:

Steps to Reproduce:
1. Setup a SDN AWS cluster
2. Migrated it to OVN successfully.
3. Then try to rollback to SDN

Actual results:
After enable MCO, the nodes keep in status "NotReady,SchedulingDisabled "

oc get nodes
NAME                                        STATUS                        ROLES    AGE     VERSION
ip-10-0-48-226.us-east-2.compute.internal   Ready                         master   4h10m   v1.21.1+8268f88
ip-10-0-58-254.us-east-2.compute.internal   Ready                         worker   3h58m   v1.21.1+8268f88
ip-10-0-61-109.us-east-2.compute.internal   NotReady,SchedulingDisabled   master   4h10m   v1.21.1+8268f88
ip-10-0-62-51.us-east-2.compute.internal    Ready                         worker   3h58m   v1.21.1+8268f88
ip-10-0-70-219.us-east-2.compute.internal   NotReady,SchedulingDisabled   worker   3h58m   v1.21.1+8268f88
ip-10-0-70-92.us-east-2.compute.internal    Ready                         master   4h10m   v1.21.1+8268f88

Expected results:
Rollback to SDN successfully.

Additional info:

Comment 8 errata-xmlrpc 2021-10-18 17:44:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.