[
https://issues.apache.org/jira/browse/CASSANDRA-15901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151874#comment-17151874
]
Berenguer Blasi commented on CASSANDRA-15901:
---------------------------------------------
So it seems after all the back and forth and given the current restrictions
mainly:
* Not providing a synthetic address load which the test actually doesn't need
* Avoiding failing on mis-config nodes
Adding a 3rd fallback seems reasonable enough, moving from failing scenarios to
a 'localhost' listen in a major release. Both {{getLocalHost()}} and
{{getLoopbackAddress()}} may fail under some OS/ip configs so we're not anyway
worse than we used to be.
The change has been pushed. It's undergoing review and an initial test run
[fired|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/161/].
Iirc at least the JMXAuth test is a legit failure I need to look into. Once
that's done I'll run a full test suite as this is touching C* code: dtests,
unit tests, jvm, etc...
> Fix unit tests to load test/conf/cassandra.yaml (so to listen on a valid ip)
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-15901
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15901
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
> Reporter: Berenguer Blasi
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.0-rc
>
>
> Many of the ci-cassandra jenkins runs fail on {{ip-10-0-5-5: Name or service
> not known}}. CASSANDRA-15622 addressed some of these but many still remain.
> Currently test C* nodes are either failing or listening on a public ip
> depending on which agent they end up.
> The idea behind this ticket is to make ant force the private VPC ip in the
> cassandra yaml when building, this will force the nodes to listen on the
> correct ip.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
