Closed joelsdc closed 2 years ago
Currently when a running the discovery phase the script checks for Cassandra nodes and exits if detects a match: https://github.com/datastax/diagnostic-collection/blob/744e043562abfc145aa2e9fb4642209e2778c8c0/ds-collector/ds-collector#L147-L151
Say, for example, you have a 15 Cassandra node cluster, with IPs:
192.168.0.1/24 ... 192.168.0.15/24
And your bastion host has the IP 192.168.0.100
192.168.0.100
When running the above check, the bastion IP of 192.168.0.100 would be a match with Cassandra node 192.168.0.10 and thus the script errors out.
192.168.0.10
This patch fixes that.
Added!
@mieslep do you wanna eyeball this too?
Currently when a running the discovery phase the script checks for Cassandra nodes and exits if detects a match: https://github.com/datastax/diagnostic-collection/blob/744e043562abfc145aa2e9fb4642209e2778c8c0/ds-collector/ds-collector#L147-L151
Say, for example, you have a 15 Cassandra node cluster, with IPs:
And your bastion host has the IP
192.168.0.100
When running the above check, the bastion IP of
192.168.0.100
would be a match with Cassandra node192.168.0.10
and thus the script errors out.This patch fixes that.