From 98083de90a1e0c8ac31cb42ea02836c02c13e778 Mon Sep 17 00:00:00 2001 From: ydiakov Date: Tue, 29 Sep 2026 10:37:33 +0800 Subject: [PATCH] Fix rosa-sts-e2e readiness check for managed-cluster-validating-webhooks The rosa-sts-e2e presubmit omits OPERATOR_RESOURCE_KIND, so the rosa-operator-e2e readiness check falls back to its "deployment" default. managed-cluster-validating-webhooks ships as a DaemonSet on OSD/ROSA Classic, so the check never finds deployment/validation-webhook and the job fails after the 120s timeout even though the DaemonSet pods are Running 1/1. Set OPERATOR_RESOURCE_KIND: daemonset to match the existing rosa-sts-e2e-promotion-int and rosa-sts-e2e-promotion-stage tests, which already set it. The job has run_if_changed on go.mod/go.sum/test/e2e, so this surfaces on any dependency-bump PR. Co-Authored-By: Claude Opus 5 --- .../openshift-managed-cluster-validating-webhooks-master.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/ci-operator/config/openshift/managed-cluster-validating-webhooks/openshift-managed-cluster-validating-webhooks-master.yaml b/ci-operator/config/openshift/managed-cluster-validating-webhooks/openshift-managed-cluster-validating-webhooks-master.yaml index 4b66c8a21a2bc..0abc7f3e3ffa5 100644 --- a/ci-operator/config/openshift/managed-cluster-validating-webhooks/openshift-managed-cluster-validating-webhooks-master.yaml +++ b/ci-operator/config/openshift/managed-cluster-validating-webhooks/openshift-managed-cluster-validating-webhooks-master.yaml @@ -68,6 +68,7 @@ tests: OPERATOR_DEPLOYMENT_NAME: validation-webhook OPERATOR_NAME: managed-cluster-validating-webhooks OPERATOR_NAMESPACE: openshift-validation-webhook + OPERATOR_RESOURCE_KIND: daemonset post: - ref: rosa-mcvw-cleanup - ref: rosa-cluster-lease-checkin