[
https://issues.apache.org/jira/browse/CASSANDRA-15901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147668#comment-17147668
]
Berenguer Blasi commented on CASSANDRA-15901:
---------------------------------------------
[~mck] CI
[runs|https://app.circleci.com/pipelines/github/bereng/cassandra/51/workflows/e5aeb0d3-9bc6-43d1-a45c-8c6f6c3412b1]
seem ok & tests pass locally as well, besides the OOM but circle was on a
partial outage today... Do you think you could run the PR against cassandra13
and see if the issue has been sorted?
> 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
