[CASSANDRA-15952] TestBootstrap::test_bootstrap_binary_disabled_resumable_bootstrap checks non-existent log messages for 3.0 and 3.11

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.22, 3.11.8
• Component/s: Test/dtest/python
• Bug Category: Correctness - Test Failure
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: Adhoc Test
• Platform: All
• Since Version: 3.0.0

Source Control Link

https://github.com/apache/cassandra-dtest/commit/94ce5797ae5892e2952fa55efd0594b1aa0e3aa8

Test and Documentation Plan

Verify that test_bootstrap_binary_disabled works against 3.0 and 3.11, and that the newly returned test_resumable_bootstrap works as well

• Assignee: Caleb Rackliffe
• Reporter: Caleb Rackliffe

Authors

Caleb Rackliffe

Reviewers

Brandon Williams, Ekaterina Dimitrova

• Created: 16/Jul/20 18:06
• Updated: 17/Jul/20 16:45
• Resolved: 17/Jul/20 16:29

Description

CASSANDRA-14525 added a bit of logging only in trunk that TestBootstrap::test_bootstrap_binary_disabled_resumable_bootstrap assumes is present in all versions. This should be as simple as making sure we only assert around that on 4.0+.

See https://app.circleci.com/pipelines/github/maedhroz/cassandra/57/workflows/b408ce8a-ee68-47bf-b9f1-eb9541e9827e/jobs/312

Issue Links

• is caused by: CASSANDRA-14525 streaming failure during bootstrap makes new node into inconsistent state
• is related to: CASSANDRA-15667 StreamResultFuture check for completeness is inconsistent, leading to races