Git does not preserve execute permissions on CI runners. Adding explicit chmod step before running deploy/teardown scripts fixes exit code 126.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
- Check all required permissions (not just delete configmaps) before deploy
- Dump pod state, events, and logs on rollout or service unreachability failures
- Improves debuggability of E2E deployment failures in CI
Co-Authored-By: Paperclip <noreply@paperclip.ing>
The argocd-plugin uses pnpm (packageManager: pnpm@10.32.1) but the
original inline workflow used npm commands (npm ci, cache: npm).
This caused the workflow to fail.
Switch to pnpm detection and commands while preserving the
E2E_RELEASE=headlamp-e2e-argocd setting required by the deploy script.
The lockfile had 'overrides' section that no longer exists in package.json,
causing 'pnpm install --frozen-lockfile' to fail with config mismatch error.
Regenerated lockfile to match current package.json state.
The argocd plugin uses pnpm (packageManager: pnpm@10.32.1) but the
inline workflow was using npm-based commands (npm ci, cache: npm).
This caused 'Setup Node.js' to fail because setup-node@v6 with
cache: npm has issues when no package-lock.json exists.
Switch to the reusable plugin-e2e workflow which properly detects
and uses pnpm for projects with pnpm-lock.yaml.
Chris Farhood
privilegedescalation-engineer[bot]