For upgrade tests correctly use cassandra_version over version, and set protocol_version to highest source version supports #275
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.
This PR…
1. Fix places where we need to be using
cassandra_version()
(instead of justversion()
), now that we support other cluster types.2. for upgrade tests default the protocol_version to the max of the source/starting version in the upgrade path -- the assumption here is that from.max_proto_v will always be within the to.min_proto_v to to.max_proto_v range.
3. for upgrade tests default the endpoint_snitch yaml property to SimpleSnitch. this relates to HCD-129
4. after upgrading a node, check and prune any unsupported config options
5. when creating a cluster (
dtest_setup.create_ccm_cluster(..)
) use the correct cluster type subclass6. when upgrading, check (and change if necessary) the cluster class type and the node class type (and copy config files into new config locations)