Upgrade k8ssandra-client to fix cassandra.yaml cluster name setting issue when running 4.1+ #1114
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does:
Updates the version of k8ssandra-client to v0.2.2 which has a fix for the cluster name issue with Cassandra 4.1+ (the name "Test Cluster" was always used).
Since this was creating issues with Reaper (as reported in #1112), one of the Reaper e2e test was modified to run against Cassandra 4.1.2.
Another tiny bug was fixed here as well: Running
CreateSingleReaper
would run bothCreateSingleReaper
andCreateSingleReaperWStargateAndHTTP
e2e tests since they begin with the same string. That makesCreateSingleReaperWStargateAndHTTP
run twice since it's also ran separately.Renaming
CreateSingleReaper
toCreateSingleReaperNoHttp
fixes the issues.Which issue(s) this PR fixes:
Fixes #1110
Fixes #1112
Checklist
Documentation added/updated