Merge pull request #78460 from JoeAldinger/OSDOCS-34823

OSDOCS-34823: updates migration procedure SDN to OVN-K

Author: JoeAldinger

modules/nw-ovn-kubernetes-migration.adoc

@@ -35,7 +35,39 @@ Perform the migration only when an interruption in service is acceptable.
 $ oc get Network.config.openshift.io cluster -o yaml > cluster-openshift-sdn.yaml
 ----
 
-. To prepare all the nodes for the migration, set the `migration` field on the Cluster Network Operator configuration object by entering the following command:
+. Verify that the  `OVN_SDN_MIGRATION_TIMEOUT` environment variable is set and is equal to `0s` by running the following command:
++
+[source,bash]
+----
+#!/bin/bash
+
+if [ -n "$OVN_SDN_MIGRATION_TIMEOUT" ] && [ "$OVN_SDN_MIGRATION_TIMEOUT" = "0s" ]; then
+    unset OVN_SDN_MIGRATION_TIMEOUT
+fi
+
+#loops the timeout command of the script to repeatedly check the cluster Operators until all are available.
+
+co_timeout=${OVN_SDN_MIGRATION_TIMEOUT:-1200s}
+timeout "$co_timeout" bash <<EOT
+until
+  oc wait co --all --for='condition=AVAILABLE=True' --timeout=10s && \
+  oc wait co --all --for='condition=PROGRESSING=False' --timeout=10s && \
+  oc wait co --all --for='condition=DEGRADED=False' --timeout=10s;
+do
+  sleep 10
+  echo "Some ClusterOperators Degraded=False,Progressing=True,or Available=False";
+done
+EOT
+----
+
+. Remove the configuration from the Cluster Network Operator (CNO) configuration object by running the following command:
++
+[source,terminal]
+----
+oc patch Network.operator.openshift.io cluster --type='merge' /  --patch '{"spec":{"migration":null}}'
+----
+
+. To prepare all the nodes for the migration, set the `migration` field on the CNO configuration object by running the following command:
 +
 [source,terminal]
 ----
@@ -48,7 +80,21 @@ $ oc patch Network.operator.openshift.io cluster --type='merge' \
 This step does not deploy OVN-Kubernetes immediately. Instead, specifying the `migration` field triggers the Machine Config Operator (MCO) to apply new machine configs to all the nodes in the cluster in preparation for the OVN-Kubernetes deployment.
 ====
 
-. Optional: You can disable automatic migration of several OpenShift SDN capabilities to the OVN-Kubernetes equivalents:
+.. Check that the reboot is finished by running the following command:
++
+[source,terminal]
+----
+$ oc get mcp
+----
+
+.. Check that all cluster Operators are available by running the following command:
++
+[source,terminal]
+----
+$ oc get co
+----
+
+.. Alternatively: You can disable automatic migration of several OpenShift SDN capabilities to the OVN-Kubernetes equivalents:
 +
 --
 * Egress IPs
@@ -293,6 +339,8 @@ daemon set "multus" successfully rolled out
 [IMPORTANT]
 ====
 The following scripts reboot all of the nodes in the cluster at the same time. This can cause your cluster to be unstable. Another option is to reboot your nodes manually one at a time. Rebooting nodes one-by-one causes considerable downtime in a cluster with many nodes.
+
+Cluster Operators will not work correctly before you reboot the nodes.
 ====
 
 ** With the `oc rsh` command, you can use a bash script similar to the following: