From f9c912bde967f7299c3c1aa24e48e45febcecd94 Mon Sep 17 00:00:00 2001 From: Jiri Mencak Date: Thu, 7 Mar 2024 22:02:39 +0100 Subject: [PATCH] Remove RELEASE_VERSION from test-upstream-tuned.sh (#969) Starting with PR858, we can no longer use a random RELEASE_VERSION to trigger daemonset/operand updates. In the context of testing upstream TuneD this is causes an issue. Not changing RELEASE_VERSION at all is a simple fix, because we are also adjusting CLUSTER_NODE_TUNED_IMAGE and that will cause a daemonset/operand update. Co-authored-by: Jiri Mencak --- hack/test-upstream-tuned.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hack/test-upstream-tuned.sh b/hack/test-upstream-tuned.sh index 7c03b85c7..1a073c3c0 100755 --- a/hack/test-upstream-tuned.sh +++ b/hack/test-upstream-tuned.sh @@ -31,7 +31,7 @@ cvo_scale() { nto_deploy_custom() { oc project openshift-cluster-node-tuning-operator - oc patch deploy cluster-node-tuning-operator -p '{"spec":{"template":{"spec":{"containers":[{"env":[{"name":"RELEASE_VERSION","value":"'$TAG'"},{"name":"CLUSTER_NODE_TUNED_IMAGE","value":"'$IMAGE'"}],"name":"cluster-node-tuning-operator"}]}}}}' + oc patch deploy cluster-node-tuning-operator -p '{"spec":{"template":{"spec":{"containers":[{"env":[{"name":"CLUSTER_NODE_TUNED_IMAGE","value":"'$IMAGE'"}],"name":"cluster-node-tuning-operator"}]}}}}' } wait_for_updated_tuned_pods() {