action #42056
closed
[sle] test fails in pvusb_run: PVUSB_DEVICE is not properly set in workers.ini
Added by michalnowak over 5 years ago.
Updated over 2 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-x86_64-virt-pvusb-sles15fcs-fv-on-developing-xen@64bit-ipmi fails in
pvusb_run
The error message is: "PVUSB_DEVICE is not properly set in workers.ini".
Worker setup:
"WORKER_CLASS" : "64bit-ipmi",
"WORKER_HOSTNAME" : "10.160.2.26",
"WORKER_ID" : 1114,
"WORKER_INSTANCE" : 3,
It works (https://openqa.suse.de/tests/2118690) with:
"WORKER_CLASS" : "64bit-ipmi",
"WORKER_HOSTNAME" : "10.162.2.88",
"WORKER_ID" : 897,
"WORKER_INSTANCE" : 1,
pvusb testcases need usb device be attached in server, and need PVUSB_DEVICE setup for worker in https://gitlab.suse.de/openqa/salt-pillars-openqa/blob/master/openqa/workerconf.sls
openqaworker13:3 worker was added for kernel bare metal testing, which is missing the above setups.
there are 2 options:
option1: add usb device(such as usb pen or keyboard) to server openqaipmi5.qa.suse.de, and add PVUSB_DEVICE setup to openqaworker13:3 worker, (need Nick's help)(poo#36961 for example)
option2: add one more worker_class(such as usb-64bit-ipmi) to below workers, and bounding pvusb testcases with this worker_class
openqaw1:1
openqaw1:2
openqaworker2:23
openqaworker2:24
openqaworker2:25
openqaworker2:26
Personally, I prefer option2 as 6 servers are enough for scheduling pvusb testcases, and we can't expect all servers in future to have the additional usb device ;)
@Santi, @Nick, we need your kindly suggestion :)
- Priority changed from Normal to Low
- Status changed from New to Resolved
Also available in: Atom
PDF