Israel Fruchter

happens again this week run, `disrupt_add_drop_column` is happening first, and then `disrupt_terminate_and_replace_node`, but doesn't seem like they are running at the same time... regardless lots of nemesis are being skipped,...

@roy have a PR that should be addressing this

> > @roy have a PR that should be addressing this > > Do I? Maybe you mixed it with another PR I have for the 200k rows? my mistake...

@vponomaryov this sound like a scylla issue, not SCT schema and topology changes are not supposed to be affecting each other, nor the load like that. SCT isn't doing something...

@vponomaryov please raise a core issue for this one, schema changes should be forcing out to pick higher RF. if it does it's a regression.

Not reproduced for quite some time

we don't have the function of selecting a docker image, so we can close this one

I've found one also in eu-west-1, from a different job I'm guessing we are not waiting for instances deletion, and we might get to this part of code, when instances...

anyhow there seems to be a retry on top of it ``` @retrying(n=30, sleep_time=10, allowed_exceptions=(ClientError,)) ``` maybe we should just squelch the errors from being printed

@soyacz still happening ?