Description of problem: SDN migration rollback failed, stuck in MCO Version-Release number of selected component (if applicable): 4.9.0-0.nightly-2021-08-03-200806 How reproducible: Always 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:
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. https://access.redhat.com/errata/RHSA-2021:3759