Israel Fruchter

> Perhaps a workaround in the tests would be to first wait for all nodes to see the restarted node as UP, and only then do the `wait_for_cql`. This way,...

@kbr-scylla see https://github.com/search?q=repo%3Ascylladb%2Fscylla-dtest%20wait_reconnection&type=code which kind of equivalent to `wait_for_cql`, and it's used only in 4 specific tests in dtest

> Is this with `consistent_cluster_management: true`? If not, concurrent schema changes are not supported by scylla and this is a known issue since forver. it's enable: ``` consistent_cluster_management: true ```

> What's the scylla-tools version? Version: 2022.2.dev-0.20220330.eef4cbb20a51

this boils down to this core issue: https://github.com/scylladb/scylladb/issues/16909 and the fix for it in: https://github.com/scylladb/scylladb/pull/16969

> SCT run didn't pass, but failure is most likely unrelated to this PR (according to @fruch it's caused by [scylladb/scylla-cluster-tests#7320](https://github.com/scylladb/scylla-cluster-tests/issues/7320) ). just a general comment, I would recommend putting...

@tchaikov this is breaking rolling upgrades tests as well https://github.com/scylladb/scylla-cluster-tests/blob/6e3d34cd1b9fc6533a4e5a3874fd36ad401b9a81/upgrade_test.py#L698 and a test for GC of tomestones: https://github.com/scylladb/scylla-cluster-tests/blob/6e3d34cd1b9fc6533a4e5a3874fd36ad401b9a81/longevity_tombstone_gc_test.py#L42

On note on the removal of some code and handling of warning, keep in mind it might complex a bit the syncing with upstream (even that upstream doesn't move at...

@Lorak-mmk @avelanarius, I've added you both to: https://github.com/orgs/scylladb/teams/python-driver-maint

> > * Remove tests that use DSE-specific functionality. I don't think we support such functionality, so it would we better to yank all DSE-specific code from the driver -...