From d956ef95d10e9b5af73c86140fabab8bd1ab53bb Mon Sep 17 00:00:00 2001
From: rrasouli <rrasouli@redhat.com>
Date: Thu, 3 Sep 2026 06:13:31 +0300
Subject: [PATCH] [ote] Fix OCP-68320 test missing SpecContext parameter

Test OCP-68320 uses g.SpecTimeout() decorator but function signature
was missing the required context parameter, causing Ginkgo to fail
during test discovery with:

  Invalid NodeTimeout SpecTimeout, or GracePeriod
  [It] was passed NodeTimeout, SpecTimeout, or GracePeriod but does not have a
  callback that accepts a SpecContext or context.Context

This prevented both aws-e2e-ote and vsphere-proxy-e2e-ote jobs from
discovering any proxy tests, failing with 'no tests to run'.
---
 ote/test/e2e/proxy.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ote/test/e2e/proxy.go b/ote/test/e2e/proxy.go
index d7b18d9596..c0eb671327 100644
--- a/ote/test/e2e/proxy.go
+++ b/ote/test/e2e/proxy.go
@@ -184,7 +184,7 @@ var _ = g.Describe("[OTP][sig-windows][apigroup:config.openshift.io] Windows_Con
 
 	g.It("Smokerun-Author:rrasouli-Critical-68320-[node-proxy]-Import custom CA certificates into Windows node system store [Serial][Disruptive]",
 		g.SpecTimeout(45*time.Minute),
-		func() {
+		func(ctx g.SpecContext) {
 			const (
 				name                        = "OCP-68320-custom"
 				validity                    = "3650"