Skip to content

Conversation

@ephemeralsad
Copy link
Contributor

Problem

Related issue: #11282

The storcon_cli node-delete command currently performs immediate deletion, which can cause client-facing outages due to the lack of a graceful shutdown process.

Summary of changes

storcon_cli

  • Introduced a --force flag to node-delete for immediate deletion without draining (current functionality).
  • By default (when --force is not set), the command now initiates a graceful drain of the node before deletion.
  • Implemented status reporting to track the draining progress.

@github-actions
Copy link

github-actions bot commented May 30, 2025

8492 tests run: 7899 passed, 11 failed, 582 skipped (full report)


Failures on Postgres 17

Failures on Postgres 16

Failures on Postgres 15

Failures on Postgres 14

# Run all failed tests locally:
scripts/pytest -vv -n $(nproc) -k "test_drain_with_secondary_locations[release-pg14] or test_drain_with_secondary_locations[release-pg14] or test_drain_with_secondary_locations[release-pg15] or test_drain_with_secondary_locations[release-pg15] or test_drain_with_secondary_locations[release-pg16] or test_drain_with_secondary_locations[release-pg16] or test_drain_with_secondary_locations[release-pg17] or test_drain_with_secondary_locations[release-pg17] or test_drain_with_secondary_locations[debug-pg17] or test_drain_with_secondary_locations[release-pg17] or test_drain_with_secondary_locations[release-pg17]"
Flaky tests (1)

Postgres 17

Test coverage report is not available

The comment gets automatically updated with the latest test results
53bdbdf at 2025-06-11T06:44:51.754Z :recycle:

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.

2 participants