Project

General

Profile

Actions

action #152446

closed

openqaworker-arm21 is broken and produces lots of incomplete jobs

Added by ggardet_arm about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Start date:
2023-12-12
Due date:
% Done:

0%

Estimated time:
Tags:

Description

openqaworker-arm21 is broken and produces lots of incomplete jobs, see:
https://openqa.opensuse.org/tests/overview?version=Tumbleweed&groupid=3

One occurrence is: https://openqa.opensuse.org/tests/3803811


Related issues 1 (0 open1 closed)

Related to openQA Infrastructure (public) - action #134123: Setup new PRG2 openQA worker for o3 - two new arm workers size:MResolvednicksinger

Actions
Actions #1

Updated by okurz about 1 year ago

  • Related to action #134123: Setup new PRG2 openQA worker for o3 - two new arm workers size:M added
Actions #2

Updated by okurz about 1 year ago

  • Status changed from New to In Progress
  • Assignee set to nicksinger
  • Priority changed from Immediate to High
  • Target version set to Ready

@ggardet_arm sorry about that. nicksinger is setting up the machine as part of #134123. I already asked him to only enable production worker classes after additional verification. I now set

WORKER_CLASS = openqaworker-arm21,qemu_aarch64_poo134123,qemu_aarch64_lse_poo134123

and triggered a reboot of the machine so the machine should not pick up and destroy more jobs for now. I then called

WORKER=openqaworker-arm21 failed_since=2023-12-11 ./openqa-advanced-retrigger-jobs

with openqa-advanced-retrigger-jobs from https://github.com/os-autoinst/scripts/blob/master/openqa-advanced-retrigger-jobs

@nicksinger to follow up.

Actions #3

Updated by okurz about 1 year ago

  • Tags set to infra
Actions #4

Updated by nicksinger about 1 year ago

  • Status changed from In Progress to Resolved

as stated in https://progress.opensuse.org/issues/134123#note-53 I was missing the correct huge table config for grub and adjusted accordingly now. I'm changing the machine back to production again as I was able to validate it can successfully run tests now. Please reopen if you observe further issues specific to that machine.

Actions

Also available in: Atom PDF