You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently scale-ci-deploy is using below command to patch ovn image
oc -n openshift-network-operator set env deployment.apps/network-operator OVN_IMAGE={{openshift_ovn_image}} RELEASE_VERSION="5.0.0"`
Howerver this patching is failing because of specifying RELEASE_VERSION.
network-operator pod is stuck in "CrashLoopBackOff" state
[root@ip-172-31-32-243 venkataanil-ovn-4.14-aws-ovn-large-cp]# oc -n openshift-network-operator get all
Warning: apps.openshift.io/v1 DeploymentConfig is deprecated in v4.14+, unavailable in v4.10000+
NAME READY STATUS RESTARTS AGE
pod/network-operator-b8549fd9d-5mxbf 0/1 CrashLoopBackOff 8 (53s ago) 46m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/metrics ClusterIP None <none> 9104/TCP 69m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/network-operator 0/1 1 0 69m
NAME DESIRED CURRENT READY AGE
replicaset.apps/network-operator-b8549fd9d 1 1 0 46m
replicaset.apps/network-operator-d77fcbf59 0 0 0 69m
We are not sure why we are overriding RELEASE_VERSION when we only want OVN_IMAGE to get overriden. To fix this issue we should only override OVN_IMAGE when user wanted ovn patching.
The text was updated successfully, but these errors were encountered:
venkataanil
added a commit
to venkataanil/scale-ci-deploy
that referenced
this issue
Oct 17, 2023
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
Fixescloud-bulldozer#218
venkataanil
added a commit
to venkataanil/scale-ci-deploy
that referenced
this issue
Oct 17, 2023
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
Fixescloud-bulldozer#218
Currently scale-ci-deploy is using below command to patch ovn image
Howerver this patching is failing because of specifying RELEASE_VERSION.
network-operator pod is stuck in "CrashLoopBackOff" state
network-opertor log is showing below stacktrace
We are not sure why we are overriding RELEASE_VERSION when we only want OVN_IMAGE to get overriden. To fix this issue we should only override OVN_IMAGE when user wanted ovn patching.
The text was updated successfully, but these errors were encountered: