Israel Fruchter

> > Is there room for export, so we can handle long term retention in another tool? > > @peterlandry definitely considering raw data export - it will be for...

> Backports are not automatically updated in any way and that's not something we're planning to do. Best case would be to be able to recreate a backport, which would...

also trying using `@mergify rebase` command, which in this situations, cause more harm, and all of the conflicts in code are duplicated, and it ends up harder to solve them....

> @syuu1228 - https://jenkins.scylladb.com/view/siren/job/siren-jobs/job/siren-backend-e2e-manual/8363/ from the looks of it, it's the same thing as we seen in SCT https://github.com/scylladb/scylla-cluster-tests/pull/11260/commits/7b47962071b553b4a573df4360ff1ae9e002b4d3 I would guess the `/etc/apt/keyrings` has the wrong permission, cause of...

@syuu1228 both look like https://github.com/scylladb/scylladb/issues/24428, which can be ignored for the sake of testing this change.

it's gemini for sure, but we are not planning to backport the new gemini version with fixes to that branch

@CodeLieutenant putting this into queue, as a reminder for the releases backport we need

I would recommend taking the instance type out of the cluster prints, and move every print that refer to a node, to the node logger and add the instance type...

from the QA chat: ``` Yulia Yakovlev, Tue 6:15 PM also received the error. As I see from the code, if scylla_version is set, it starts to get arch from...

to sum it up, both sct_config.py and `get_arch_from_instance_type` can be change to be safer and have sane defaults