Fix flaky E2E test checking in-cluster shardawareness #1038
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.
Both on CI and on local environments traffic between test binary and
Scylla Pods is NATed. Previous implementation gave false positives
because we are low on resources (we use just 2 shards) so probability of
hitting expected shard was high even for random assignment.
It wasn't spotted because message about wrong shard assignment is
printed out by the driver to stdout and no error is reported anywhere.
Gocql doesn't expose any way of checking if shardaware ports are used
successfully, hence I implemented simple driver within a test, able to
send initial packet and reading to which shard connection was established.
It also check in-cluster connectivity which is how clients are
connecting from, compared to from outside in previous appraoch.
Fixes #1028
Requires: