Israel Fruchter

Regardless there are two options to avoid this one: 1) run it on Jenkins job 2) take an older branch, i.e. branch-2023.1, that doesn't have the new AMI project support

> Thanks. > @fruch have you already sent this request of should I? > In case this is the later, what are the roles I should ask assume permissions for?...

> My proposal: > 1. init resources: do all nodes in parallel (should be easy) or move syslogng/ssh setup to cloud init (like in Azure) so the initial gap for...

> > init monitor nodes: 892s > > > > * init wrap: 891s (`TestConfig duration`) > > Do we have logs for this? yes, and in other PR we...

closing this one in favor of https://github.com/scylladb/qa-tasks/issues/1650 where we track the different tasks we have for this effort

Timestamp in the filenames in the fallocate commands, are matching 13:51 So this is the actual command from the enospc nemesis, but nothing explains how they were run again... So...

> I think this is our old friend 'log duplication' - see that after these hours we see exactly the same PID's of scylla, just logs repeats. > I remember...

> > > I think this is our old friend 'log duplication' - see that after these hours we see exactly the same PID's of scylla, just logs repeats. >...

@soyacz yes, now I see it's the exact same timestamp on the command itself, and it was caused by the hard reboot after hard reboot we configured the logging system...

here's one example of such occurrence: ``` # SCT starts compressing 2024-02-25T22:13:05.713+00:00 multi-dc-rackaware-tablets--db-node-7a99b942-5 !NOTICE | sudo[17453]: scyllaadm : PWD=/home/scyllaadm ; USER=root ; COMMAND=/usr/bin/pigz --fast --keep /var/lib/systemd/coredump/core.scylla.112.7ca8b11c592f4c37b5e4e54b56772b37.17368.1708899083000000 ... # systemd-coredump decides...