Skip to content

tester.py: downgrade 'no such container' errors on teardown #11430

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

cezarmoise
Copy link
Contributor

If a nemesis happens to start a cassandra stress container just as teardown starts, it is possible the container is removed faster than the nemesis can be stopped, and it will try to use it and fail.

Added enable_teardown_filters, a parallel to enable_default_filters.

Example of occurrence: https://jenkins.scylladb.com/job/scylla-2025.2/job/features/job/FIPS/job/longevity-100gb-4h-fips-test/12/consoleFull

Testing

  • [ ]

PR pre-checks (self review)

  • I added the relevant backport labels
  • I didn't leave commented-out/debugging code

Reminders

  • Add New configuration option and document them (in sdcm/sct_config.py)
  • Add unit tests to cover my changes (under unit-test/ folder)
  • Update the Readme/doc folder relevant to this change (if needed)

If a nemesis happens to start a cassandra stress container just as teardown starts,
it is possible the container is removed faster than the nemesis can be stopped,
and it will try to use it and fail.

Added `enable_teardown_filters`, a parallel to `enable_default_filters`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant