[
https://issues.apache.org/jira/browse/CASSANDRA-15901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150300#comment-17150300
]
Michael Semb Wever commented on CASSANDRA-15901:
------------------------------------------------
bq. Well, the most unintrusive way would be to add the hostname to the
127.0.0.1 (or even better the host's public IP) entry in /etc/hosts.
These tests have also failed in the previous jenkins environment at
builds.apache.org (long before circleci was introduced).
The jenkins agents require public ip and a valid hostname. So there is a valid
reason that these nodes are "not properly configured" (according to our
definition for a runtime node).
And, we don't have ssh access. So this may be un-intrusive to code changes, but
involves either waiting a few weeks or months for the owner of the donated
agents to re-configure them (to incorrectly let tests listen on public
interfaces), or containerising all tests (bc inside containers hostname can
always safely be the private interface, like circleci).
bq. … those are "pure" unit tests (i.e. don't need a daemon or any
configuration)
I'm not sure I agree entirely with that statement. But those quotes imply you
don't either. These unit tests are not really configuration free, the fault
lies in the fact that the tests are looking up the configuration, and those
that haven't defined the config then fall back onto an opinion that is
incompatible with the "jenkins agents around the world but unlike normal C*
don't listen on the public interface because this is tests" setup. A pure unit
test shouldn't be resorting to either an opinion or an OS hostname lookup. A
hardcoded default config would be more appropriate, in theory. But alas the C*
is a bit too messy for the ideal :-(
Thanks for pushing back [~snazy].
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
