Skip to content

[main]Fix(ci): fix delete-env failures and add force-delete fallback#3819

Open
prkalle wants to merge 1 commit into
cloudfoundry:mainfrom
prkalle:fix/force_delete-env_main
Open

[main]Fix(ci): fix delete-env failures and add force-delete fallback#3819
prkalle wants to merge 1 commit into
cloudfoundry:mainfrom
prkalle:fix/force_delete-env_main

Conversation

@prkalle

@prkalle prkalle commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Description of the Change

This PR fixes delete-env failures during CI teardown. This PR fixes adds a force-delete fallback that tears down the environment directly via the GCP CPI when the graceful path still can't recover (e.g. an unresponsive director).

Why Is This PR Valuable?

It prevents resource leaks that were silently accumulating cost every time delete-env failed to fully tear down a test environment.

Applicable Issues

List any applicable GitHub Issues here

How Urgent Is The Change?

moderately urgent

Other Relevant Parties

bosh delete-deployment used an invalid --skip-drain flag, causing it to
silently fail every run and leaving bbl down to hit "umount: target is
busy" during its own deployment teardown. Fix the flag and add a
force-delete-env.sh fallback that tears down the director/jumpbox directly
via the GCP CPI when the graceful path can't recover (e.g. abandoned BOSH
tasks or a stuck task worker).

Signed-off-by: Prem Kumar Kalle <prem.kalle@broadcom.com>
@prkalle prkalle force-pushed the fix/force_delete-env_main branch from e42d486 to a5ddb70 Compare July 11, 2026 00:15
@prkalle prkalle changed the title Fix(ci): fix delete-env failures and add force-delete fallback [main]Fix(ci): fix delete-env failures and add force-delete fallback Jul 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant