openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Code Issues Releases Activity

Reorders sdn to ovnk rollback procedure

Browse Source
This commit is contained in:
Steven
2024-04-23 15:06:37 -04:00
committed by openshift-cherrypick-robot
parent 745d2b25a8
commit ae27fdfed7
1 changed files with 21 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
modules/nw-ovn-kubernetes-rollback.adoc
View File

@@ -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: