Israel Fruchter

Me and @roy found the reason for external communication, SG was open for ssh, we close it as it should have been. As for the network issue we are facing...

@juliayakovlev please look at this one, seems like we are having an issue with multiple network not working after node is rebooted.

@juliayakovlev what is this log, in the last comment? The context of it isn't clear

> I ran the tests with `disrupt_multiple_hard_reboot_node` only - the problem was not reproduced Can you try running it with the scylla version from reported failures ? If that doesn't...

just to sum the observation so far, me and @juliayakovlev found after node reboot, 2nd interface isn't functioning, doing `sudo netplan apply` seems to be fixing it. trying now, to...

> Created branch `issue_sct_8553`. The change there - do not run `sdcm.provision.aws.utils.configure_eth1_script`, not re-configure secondary network interface. > > Run 2 tests: > 1. Test with `disrupt_multiple_hard_reboot_node` only - PASSED....

we are using docker `--dns` flag exactly like that in SCT: https://github.com/scylladb/scylla-cluster-tests/blob/052e07b4b188e2998ed933d5f4c3faabb76a1b57/sdcm/ycsb_thread.py#L266 and the java cache disablement: https://github.com/scylladb/scylla-cluster-tests/blame/052e07b4b188e2998ed933d5f4c3faabb76a1b57/docker/ycsb/Dockerfile#L30

@roydahan have you seen this one ?

> Maybe it's a good opportunity to verify defaults shipped with AMI? Could be in followup too if we want it. defaults you mean the content of `io_properites.yaml` ?

> > > Maybe it's a good opportunity to verify defaults shipped with AMI? Could be in followup too if we want it. > > > > > > defaults...