Actions
action #49520
closed[functional][u] Add an extra unique worker class to each worker host
Start date:
2019-03-20
Due date:
% Done:
0%
Estimated time:
Difficulty:
easy
Description
Motivation¶
Sometimes a bug happens in a specific worker host. When trying to debug, we don't have a way of specifying in a job, which worker host to pick.
It would be useful for debugging to have a unique worker class name, so that a job can be set up to pick a worker instance from a specific worker host.
Suggestions¶
https://gitlab.suse.de/openqa/salt-states-openqa/blob/master/openqa/workers.ini:
Example output:
openqaworker13:
# 16 cores
...
global:
WORKER_CLASS: openqaworker13,qemu_amd64,qemu_x86_64_staging
malbec:
numofworkers: 4
...
global:
QEMUTHREADS: 1
WORKER_CLASS: malbec,qemu_ppc64le,qemu_ppc64le_no_tmpfs,tap
Acceptance criteria¶
- AC1: A job can be set up to be picked by a specific worker host.
- AC2: Worker hostname is added as worker class automatically by salt.
Updated by SLindoMansilla over 5 years ago
- Related to action #48635: [functional][u] test fails in kvm - no svm flag for openqaworker13 (AMD worker) added
Updated by SLindoMansilla over 5 years ago
- Description updated (diff)
This could unblock the high prio ticket: #48635
Updated by SLindoMansilla over 5 years ago
- Assignee set to szarate
Assigning to you as a reminder.
As spoken, could you check if this is a duplicate of an already existing ticket?
Updated by SLindoMansilla over 5 years ago
- Description updated (diff)
- Status changed from New to Workable
Updated by SLindoMansilla over 5 years ago
- Status changed from Workable to Rejected
As duplicate of #27811
Updated by SLindoMansilla over 5 years ago
- Related to deleted (action #48635: [functional][u] test fails in kvm - no svm flag for openqaworker13 (AMD worker))
Updated by SLindoMansilla over 5 years ago
- Related to action #48635: [functional][u] test fails in kvm - no svm flag for openqaworker13 (AMD worker) added
Actions