Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
4.12
-
Important
-
OCPNODE Sprint 230 (Blue), OCPNODE Sprint 238 (Blue)
-
2
-
False
-
Description
Description of problem:
[Alicloud] sdn2ovn migration rollback failed on network operator not available
Version-Release number of selected component (if applicable):
4.12.0-0.nightly-2022-12-19-150237
How reproducible:
Always
Steps to Reproduce:
1. Run sdn2ovn migration script in Alicloud: https://github.com/openshift/release/blob/master/ci-operator/step-registry/ovn/sdn-migration/ovn-sdn-migration-commands.sh 2. Run sdn2ovn migration rollback script in Alicloud: https://github.com/openshift/release/blob/master/ci-operator/step-registry/ovn/sdn-migration-rollback/ovn-sdn-migration-rollback-commands.sh
Actual results:
Only network operator is not available
Expected results:
network operator is available
Additional info:
After rollback, the 80-openshift-network.conf is missing under /etc/cni/net.d . But it exists under /var/run/multus/cni/net.d/ .
Attachments
Issue Links
- account is impacted by
-
OCPNODE-1418 Fix propagation status in Kubelet
- Closed