Merge pull request #75039 from stevsmit/OCPBUGS-32528

Reorders sdn to ovnk rollback procedure

Author: stevsmit

modules/nw-ovn-kubernetes-rollback.adoc

@@ -139,25 +139,7 @@ $ oc patch Network.operator.openshift.io cluster --type=merge \
     }}}}'
 ----
 
-. Wait until the Multus daemon set rollout completes.
-+
-[source,terminal]
-----
-$ oc -n openshift-multus rollout status daemonset/multus
-----
-+
-The name of the Multus pods is in form of `multus-<xxxxx>` where `<xxxxx>` is a random sequence of letters. It might take several moments for the pods to restart.
-+
-.Example output
-[source,text]
-----
-Waiting for daemon set "multus" rollout to finish: 1 out of 6 new pods have been updated...
-...
-Waiting for daemon set "multus" rollout to finish: 5 of 6 updated pods are available...
-daemon set "multus" successfully rolled out
-----
-
-. To complete changing the network plugin, reboot each node in your cluster. You can reboot the nodes in your cluster with either of the following approaches:
+. Reboot each node in your cluster. You can reboot the nodes in your cluster with either of the following approaches:
 
 ** With the `oc rsh` command, you can use a bash script similar to the following:
 +
@@ -189,7 +171,26 @@ do
 done
 ----
 
-. After the nodes in your cluster have rebooted, start all of the machine configuration pools:
+
+. Wait until the Multus daemon set rollout completes. Run the following command to see your rollout status:
++
+[source,terminal]
+----
+$ oc -n openshift-multus rollout status daemonset/multus
+----
++
+The name of the Multus pods is in the form of `multus-<xxxxx>` where `<xxxxx>` is a random sequence of letters. It might take several moments for the pods to restart.
++
+.Example output
+[source,text]
+----
+Waiting for daemon set "multus" rollout to finish: 1 out of 6 new pods have been updated...
+...
+Waiting for daemon set "multus" rollout to finish: 5 of 6 updated pods are available...
+daemon set "multus" successfully rolled out
+----
+
+. After the nodes in your cluster have rebooted and the multus pods are rolled out, start all of the machine configuration pools by running the following commands::
 +
 --
 * Start the master configuration pool: