[dtest]: test_connectivity_with_cassandra_stress failed with java.lang.NoSuchMethodError

[yaronkaikov]

Following the changes made in
scylladb/scylla-tools-java#369, dtest is now failing during test_connectivity_with_cassandra_stress with the following error:

stderr: java.lang.NoSuchMethodError: 'java.lang.String com.google.common.net.HostAndPort.getHostText()'
	at com.datastax.driver.core.ScyllaCloudDatacenter.getServer(ScyllaCloudDatacenter.java:77)
	at com.datastax.driver.core.Cluster$Builder.withScyllaCloudConnectionConfig(Cluster.java:1404)
	at com.datastax.driver.core.Cluster$Builder.withScyllaCloudConnectionConfig(Cluster.java:1397)
	at com.datastax.driver.core.Cluster$Builder.withScyllaCloudConnectionConfig(Cluster.java:1393)
	at com.datastax.driver.core.Cluster$Builder.withScyllaCloudConnectionConfig(Cluster.java:1389)
	at org.apache.cassandra.stress.util.JavaDriverClient.connect(JavaDriverClient.java:181)
	at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:213)
	at org.apache.cassandra.stress.settings.SettingsSchema.createKeySpacesNative(SettingsSchema.java:84)
	at org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:74)
	at org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:230)
	at org.apache.cassandra.stress.StressAction.run(StressAction.java:58)
	at org.apache.cassandra.stress.Stress.run(Stress.java:143)
	at org.apache.cassandra.stress.Stress.main(Stress.java:62)

[Bouncheck]

LGTM, I can see that CI has for some reason terribly failed, but it seems to be unrelated.

[roydahan]

@fruch I think that the CI fails for an issue with CCM can you please take a look?

[mykaul]

@fruch I think that the CI fails for an issue with CCM can you please take a look?

Isn't it scylladb/scylla-ccm#537 and friends?

[fruch]

@fruch I think that the CI fails for an issue with CCM can you please take a look?

Isn't it scylladb/scylla-ccm#537 and friends?

yes, it's not yet handled (@k0machi was in the middle of handling it)

[roydahan]

This PR should fix the broken CI due to CCM #269.

[roydahan]

I re-ran CI, since the CI issue is fixed.

[fruch]

I re-ran CI, since the CI issue is fixed.

This PR needs to be rebase for it to work

[yaronkaikov]

I re-ran CI, since the CI issue is fixed.

This PR needs to be rebase for it to work

Rebased

[yaronkaikov]

@fruch Still some failures. are they ok?

[fruch]

@fruch Still some failures. are they ok?

I don't know, just that two of them looks like the same failures in @roydahan

MapperUDTTest.should_throw_error_when_table_is_altered_and_is_not_compatible_anymore:563 

and one new, which I don't know if related or not:

MapperTest.should_fail_when_io_thread_used:402->executeFunctionAndTestForException:534 Expected a failed future, callback was executed on Thread[cluster7-worker-2,5,main]

[roydahan]

@Bouncheck / @avelanarius , We need someone to check the new failure.

Regarding the other failures, I saw them in my other PR as well to fix the CI.
Are these known failures? Did the CI use to pass completely?

[Bouncheck]

2 out of 3 (MapperUDTTest failures) are just a matter of having a different error message in newer Scylla. This should be an easy fix.
I don't know yet why the third one fails (MapperTest.should_fail_when_io_thread_used()). Looking into that.

[avelanarius]

(Rebased on current master after #271)