action #170041
closedConfigure wireguard tunnels on hosts located in the NUE2 server room - at least one KVM@PowerNV host size:S
0%
Description
Acceptance criteria¶
- AC1: At least one KVM@PowerNV host in the NUE2 server room can work on OSD openQA tests again
Suggestions¶
- Follow steps from #169564 but focus on one KVM@PowerNV host, i.e. one of diesel+petrol+mania
- Handle any ppc64le specifics, block on product bugs, apply workaround, etc.
- Ensure KVM@PowerNV OSD jobs are picked up and executed properly again
- Remove the silence
alertname=Queue: State (SUSE) - too few jobs executed alert
from https://stats.openqa-monitor.qa.suse.de/alerting/silences
Updated by okurz about 1 month ago
- Copied from action #169564: Configure wireguard tunnels on OSD production hosts needed for openQA located in the NUE2 server room size:S added
Updated by okurz about 1 month ago
- Description updated (diff)
- Status changed from New to Blocked
Updated by okurz 30 days ago
I already installed wireguard-tools
manually now on diesel. kmod list | grep wireguard
does not list wireguard. I assume we can actually not get wireguard to run on the machines in the current state as we are running Linux 5.3 from Leap 15.3 due to regressions in newer versions, see https://bugzilla.suse.com/show_bug.cgi?id=1202138 as originally found in #114565 . We could try even newer kernels, e.g. Tumbleweed.
Updated by okurz 29 days ago
- Copied to action #170101: Use grenache-1 as KVM@PowerNV host added
Updated by okurz 23 days ago
- Due date set to 2024-12-10
- Status changed from Blocked to Feedback
- Priority changed from Low to Normal
- Target version changed from future to Ready
The nice surprise is that we can actually run wireguard on our Power8 machines with Linux 5.3 and we have first passed OSD jobs, e.g. https://openqa.suse.de/tests/16003531 . Maybe wireguard was actually backported within the SUSE kernel. So effectively this is being worked on. It just doesn't need any special handling so far. We will monitor jobs over the next days.