-
Bug
-
Resolution: Not a Bug
-
Critical
-
None
-
4.16
-
Critical
-
No
-
Proposed
-
False
-
Run below migration steps, same testing pass in AWS/GCP but fail in Azure.
$ oc get Infrastructure/cluster -o jsonpath='{.status.platformStatus.type}' Azure $ oc get network.config/cluster -o jsonpath='{.status.networkType}' OpenShiftSDN $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.16.0-0.nightly-2024-04-08-024331 True False 86m Cluster version is 4.16.0-0.nightly-2024-04-08-024331 $ oc get project | grep dedicated-admin $ oc new-project dedicated-admin Now using project "dedicated-admin" on server "https://api.weliang-4112.qe.azure.devcluster.openshift.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname $ oc patch Network.config.openshift.io cluster --type='merge' --patch '{"metadata":{"annotations":{"network.openshift.io/network-type-migration":""}},"spec":{"networkType":"OVNKubernetes"}}' network.config.openshift.io/cluster patched oc get co network -o yaml status: conditions: - lastTransitionTime: "2024-04-11T13:45:31Z" message: The cluster configuration is invalid (network type live migration is not supported on self managed clusters). Use 'oc edit network.config.openshift.io cluster' to fix. reason: InvalidClusterConfig