From 0e26d7e52ca07b7cfda04f74bd417cbd0dc50df5 Mon Sep 17 00:00:00 2001 From: venkataanil Date: Tue, 17 Oct 2023 16:49:19 +0530 Subject: [PATCH] avoid RELEASE_VERSION override during ovn patching network operator is stuck in CrashLoppBackOff state when we are overriding RELEASE_VERSION during ovn patching. The purpose of this ansible task is to only override OVN_MAGE, we will avoid changing RELEASE_VERSION in this task Fixes #218 --- OCP-4.X/roles/post-install/tasks/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OCP-4.X/roles/post-install/tasks/main.yml b/OCP-4.X/roles/post-install/tasks/main.yml index 2b4c13db..963cf680 100644 --- a/OCP-4.X/roles/post-install/tasks/main.yml +++ b/OCP-4.X/roles/post-install/tasks/main.yml @@ -203,7 +203,7 @@ - name: Patch new OVNKubernetes Image block: - name: Patch new OVNKubernetes Image - command: oc -n openshift-network-operator set env deployment.apps/network-operator OVN_IMAGE={{openshift_ovn_image}} RELEASE_VERSION="5.0.0" + command: oc -n openshift-network-operator set env deployment.apps/network-operator OVN_IMAGE={{openshift_ovn_image}} - name: Get ovnkube-node pod shell: oc get pods -n {{ ovn_namespace }} | tail -n1 | awk '{print $1}'