-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.14
-
No
-
3
-
OSDOCS Sprint 252
-
1
-
False
-
-
N/A
-
Bug Fix
-
In Progress
Description of problem:
When rolling back from OVN to OpenShift SDN, the order of the steps 6 and 7 described in the documentation is wrong. The multus pods are not going to be ready until the nodes are rebooted. So the step 7 will be needed to complete the step 6.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
100%
Steps to Reproduce:
1. Follow the Rolling back to the OpenShiftSDN network plugin (all steps until step 6)
2. The multus pods will not be ready (The pods will be in CrashLoopBackOff). The same will happen with the sdn and sdn-controller pods.
3. Reboot all nodes, the pods will start.
Actual results:
The multus pods will not be ready (The pods will be in CrashLoopBackOff). The same will happen with the sdn and sdn-controller pods.
Expected results:
The multus pods will be ok after rebooting the node. So the reboot described in step 7 is needed to complete the step 6.
Additional info:
