From fb6bdb50c91bdfc012f50f08f2e3a34f1acadf34 Mon Sep 17 00:00:00 2001 From: Chris Farhood Date: Wed, 6 May 2026 15:48:54 +0000 Subject: [PATCH] fix(e2e): add diagnostic output to RBAC apply step to diagnose remaining failure E2E still failing at step 11 after --namespace fix. Adding detailed diagnostic output to capture actual kubectl error message before it cascades. Also verifying RoleExists before apply to detect if Flux already synced the RBAC from infra repo. Ref: PRI-851 --- .github/workflows/e2e.yaml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/e2e.yaml b/.github/workflows/e2e.yaml index 975c6b7..74204fa 100644 --- a/.github/workflows/e2e.yaml +++ b/.github/workflows/e2e.yaml @@ -132,7 +132,11 @@ jobs: - name: Apply RBAC for E2E pipeline run: | set -x - kubectl apply -f deployment/e2e-ci-runner-rbac.yaml --namespace=headlamp-dev + echo "=== Verifying RBAC is available in headlamp-dev namespace ===" + kubectl get role e2e-ci-runner -n headlamp-dev && echo "Role e2e-ci-runner already exists" || echo "Role e2e-ci-runner not found" + kubectl get rolebinding e2e-ci-runner-binding -n headlamp-dev && echo "RoleBinding e2e-ci-runner-binding already exists" || echo "RoleBinding not found" + echo "Applying RBAC from deployment/e2e-ci-runner-rbac.yaml..." + kubectl apply -f deployment/e2e-ci-runner-rbac.yaml || echo "apply returned exit code $?" echo "Waiting for RBAC propagation..." sleep 5 kubectl get role e2e-ci-runner -n headlamp-dev