Loic Devulder

> JFYI: beware of k3s-io/k3s#2306 when deploying k3s/rke2 clusters with multiple nodes in parallel. You might need to add master nodes gradually or leader election might fail. Yes, the parallelization...

Support added in [helpers library](https://github.com/rancher-sandbox/ele-testhelpers/pull/45),need to be tested and implemented in E2E tests.

Is it still necessary? As we don't directly provide ISO anymore, no?

Merge/Pull Requests opened: - Test code: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19286 ✅ - Trigger scripts: https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/-/merge_requests/172 ✅ - Salt States (deployment): https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/1167 ✅ - Needles: https://gitlab.suse.de/openqa/os-autoinst-needles-sles/-/merge_requests/1663 ✅ - Jobs group definition (backup): https://github.com/rancher/elemental/pull/1397 ✅...

It seems to be a Rancher Manager issue: https://github.com/rancher/rancher/issues/44613. Move to `Blocked` column to wait for a fix or a clear state about the "culprit".

We saw the kind of issue in our CI, doesn't seem related to Elemental but we are still investing this issue. We'll keep you updated!

Fixed with PR #520.

@moio test with 160 nodes: https://github.com/rancher/elemental/actions/runs/4439953126. Last step is to be able to provision multiple clusters. After this we should have a good scalability test.

@agracey Not as I'm aware. I'm not a Rancher Manager expert at all and I have no knowledge on how to do this. If you know how to do this...

This test is not done with the UI but entirely with CLI (and all automated). If you have the same with kubectl or rancherctl command it would be easier 😉