From e90fb760f6c262e4d2e6862f8e398a787669ee2b Mon Sep 17 00:00:00 2001 From: Clint Branham Date: Wed, 25 Mar 2026 17:06:22 -0500 Subject: [PATCH] fix: use force-cleanup in CI for reliable teardown CI cleanup should always succeed regardless of Terraform state (cancelled runs, timeouts, partial failures). force-cleanup uses direct API calls + docker rm instead of terraform destroy. Co-Authored-By: Claude Opus 4.6 (1M context) --- .github/workflows/integration-tests.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/integration-tests.yml b/.github/workflows/integration-tests.yml index ae63190..d54e279 100644 --- a/.github/workflows/integration-tests.yml +++ b/.github/workflows/integration-tests.yml @@ -209,9 +209,9 @@ jobs: PVE_API_TOKEN: ${{ secrets.PVE_API_TOKEN }} PVE_TARGET_NODE: ${{ vars.PVE_TARGET_NODE }} PVE_PASSWORD: ${{ secrets.PVE_TEST_PASSWORD }} - # Terraform state is stored on the shared mount (/opt/pve-integration/work/) - # so it persists between CI jobs. - run: bash ${SCRIPTS_DIR}/run-integration.sh cleanup + # Always use force-cleanup in CI — handles corrupted state from + # cancelled runs, timeouts, or partial provisioning failures. + run: bash ${SCRIPTS_DIR}/run-integration.sh force-cleanup # ── Clean up old container images from GHCR ────────────────────────── cleanup-images: