[
https://issues.apache.org/jira/browse/CASSANDRA-15901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146160#comment-17146160
]
Berenguer Blasi commented on CASSANDRA-15901:
---------------------------------------------
After discussion with [~mck] it seems the underlying root cause is that some
tests don't init the daemon. Hence the config/listen_address are never loaded
and effective. We came up with the following course of action:
* Make all ci-cass agents fail consistently, so any new tests will get
reported.
* Fix all current tests to init the daemon correctly
* Once ci-cass is in good shape we can link the report for the commit into the
Jira ticket
* Explore ways to make that fail locally so you get the failure pre-push
rather than post-commit/ci-cass run
> Force jenkins tests to run on the private VPC 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
