Skip to content

OSDOCS-14901: Added network-type-migration- annotation step to nw-ov… #95003

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: enterprise-4.16
Choose a base branch
from
+18 −4
Open

OSDOCS-14901: Added network-type-migration- annotation step to nw-ov… #95003

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion modules/initiating-limited-live-migration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,4 +58,11 @@ $ oc get network.config.openshift.io cluster -o jsonpath='{.status.networkType}'
$ oc get network.config cluster -o=jsonpath='{.status.conditions}' | jq .
----
+
You can check limited live migration metrics for troubleshooting issues. For more information, see "Checking limited live migration metrics".
You can check limited live migration metrics for troubleshooting issues. For more information, see "Checking limited live migration metrics".

. After a successful migration operation, remove the `network.openshift.io/network-type-migration-` annotation from the `network.config` custom resource by entering the following command:
+
[source,terminal]
----
$ oc annotate network.config cluster network.openshift.io/network-type-migration-
----
13 changes: 10 additions & 3 deletions modules/nw-ovn-kubernetes-migration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -460,29 +460,36 @@ $ oc get co
The status of every cluster Operator must be the following: `AVAILABLE="True"`, `PROGRESSING="False"`, `DEGRADED="False"`. If a cluster Operator is not available or degraded, check the logs for the cluster Operator for more information.

. Complete the following steps only if the migration succeeds and your cluster is in a good state:

+
.. To remove the migration configuration from the CNO configuration object, enter the following command:
+
[source,terminal]
----
$ oc patch Network.operator.openshift.io cluster --type='merge' \
--patch '{ "spec": { "migration": null } }'
----

+
.. To remove custom configuration for the OpenShift SDN network provider, enter the following command:
+
[source,terminal]
----
$ oc patch Network.operator.openshift.io cluster --type='merge' \
--patch '{ "spec": { "defaultNetwork": { "openshiftSDNConfig": null } } }'
----

+
.. To remove the OpenShift SDN network provider namespace, enter the following command:
+
[source,terminal]
----
$ oc delete namespace openshift-sdn
----
+
.. After a successful migration operation, remove the `network.openshift.io/network-type-migration-` annotation from the `network.config` custom resource by entering the following command:
+
[source,terminal]
----
$ oc annotate network.config cluster network.openshift.io/network-type-migration-
----

.Next steps

Expand Down