[CASSANDRA-15447] in-jvm dtest support for subnets doesn't change seed provider subnet

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.16, 3.0.20, 3.11.8, 4.0-alpha3, 4.0
• Component/s: Test/dtest/java
• Labels: pull-request-available
• Bug Category: Correctness - Test Failure
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: Unit Test
• Platform: All
• Since Version: 2.2.15

Source Control Link

https://github.com/apache/cassandra/commit/fdc055da124efc92a73bd208b4463ee5528c85e0

Test and Documentation Plan

To test, back-ported the GossipSettlesTest and made it use a non-zero subnet, which will fail if the patch is not applied. See GitHub PRs for patch details.

• Assignee: Doug Rohrer
• Reporter: Doug Rohrer

Authors

Doug Rohrer

Reviewers

David Capwell, Yifan Cai

• Created: 11/Dec/19 21:48
• Updated: 16/Mar/22 12:51
• Resolved: 18/Dec/19 17:16

Description

When using the `withSubnet` function on AbstractCluster.Builder, the newly-selected subnet is never used when setting up the SeedProvider in the constructor of InstanceConfig, which is hard-coded to 127.0.0.1. Because of this, clusters with any subnet other than 0, and gossip enabled, cannot start up as they have no seed provider in their subnet and what should be the seed (instance 1) doesn't think it is the seed.

Issue Links

• links to: GitHub Pull Request #393
• links to: GitHub Pull Request #394
• links to: GitHub Pull Request #395
• links to: GitHub Pull Request #396