Skip to content

Conversation

@tarzanek
Copy link
Contributor

note this might break IPv6 IP tests

note this might break IPv6 IP tests
@tarzanek
Copy link
Contributor Author

Note:
5b65941
did in 2014 exact the opposite to get IPv6 test working

this change is needed for scylladb/scylla-tools-java#100 to pass dtest

@fruch
Copy link
Contributor

fruch commented Aug 21, 2019

@tarzanek can you take this ccm branch for a walk in the BYO with -a next-gating ?, also I don't know if this issue from 2014 is still relevant, i'll try looking for the relevant tests in dtest

@tarzanek
Copy link
Contributor Author

@tarzanek
Copy link
Contributor Author

@fruch the jenkins job failed on something completely different - can you help me figuring out if it is relevant or how to move further?

@tarzanek
Copy link
Contributor Author

@fruch
Copy link
Contributor

fruch commented Aug 25, 2019

@tarzanek looks good.

I would only want one quick eye from @bhalevy or @slivne if they know if we have any ipv6 tests in dtest that might break cause of this.

@fruch fruch requested review from bhalevy and slivne August 25, 2019 06:15
@fruch fruch self-assigned this Aug 25, 2019
@tarzanek
Copy link
Contributor Author

re: IPv6 - I think just enclosing the IP in tests into " "(or sanitizing them) would make them work, so I am puzzled the cassandra folks didn't rather fix enclosure than having a hack that depends on localhost name resolution

Copy link
Member

@bhalevy bhalevy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently the node ip addresses in dtest are all ipv4 so I see no issue.
When we support IPv6 at the ccm/dtest level we should attend to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants