QA » openQA Project » openQA Infrastructure

livdywan wrote in #note-3:

The scenario is https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Server-DVD-Updates&machine=64bit&test=ovs-client&version=15-SP5

Jobs are looking good currently e.g. on worker30+29 or worker30+37 (including on worker31 #135407#note-15).

There's one job scheduled specifically for worker31 https://openqa.suse.de/tests/12268287 which won't work because tap was taken out, hence I'm cloning that w/o the worker class.
Edit: https://openqa.suse.de/tests/12268107

Running ovs-client/server on production mm workers/31 respectively to test stability. Second build has the worker selection reversed in case it makes a difference:

• https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=poo135773_prod_spare
• https://openqa.suse.de/tests/overview?build=poo135773_prod_spare_flip&distri=sle&version=15-SP5

Running this was a bit tedious. What I ended up doing was using --export-command to prepare a -X POST job command, and then setting especially these variables:

'BUILD=poo135773_prod_spare_flip'
"TEST:12253260=ovs-server-$i"
"TEST:12253438=ovs-client-$i"
'WORKER_CLASS:12253260=qemu_x86_64,tap_poo135407,worker31'
'WORKER_CLASS:12253438=qemu_x86_64,tap'

livdywan wrote in #note-7:

I'm scheduling another batch (same group, higher indices). Let's see if jobs continue to be fine.

Well, turns out some of the repos were removed rendering the batch pointless since they all fail to install some of those repos and this is at best checked when initially cloning which I was not doing due to my use of --export-command.

• https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=poo135773_prod_spare 43/43=100% passed
• https://openqa.suse.de/tests/overview?build=poo135773_prod_spare_flip&distri=sle&version=15-SP5 100/100=100% passed (001..100)

so we are good regarding worker31. Yes, triggering those tests and tweaking is ugly. What I did now is use a SLE15-SP6 base which is less likely to need changes regarding repo settings and might be a good variant to test as well. What I did:

openqa-clone-job --export-command --skip-chained-deps --parental-inheritance --within-instance https://openqa.suse.de/tests/12207584

then copy-paste the command into the command line, delete all variables "BUILD", "_GROUP_ID", "TEST", "WORKER_CLASS" and replace those accordingly with

'TEST:12207583=ovs-client-poo135773' 'TEST:12207584=ovs-server-poo135773' 'WORKER_CLASS:12207583=qemu_x86_64,tap' 'WORKER_CLASS:12207584=worker31' _GROUP=0 BUILD=poo135773_prod_spare_flip

forming the complete command.
This triggered https://openqa.suse.de/tests/12343491

@livdywan please ensure that the workaround of "pin to individual machines" is removed everywhere and reference in #134282 how to verify other workers.

@livdywan please ensure that the workaround of "pin to individual machines" is removed everywhere and reference in #134282 how to verify other workers.

There's no remaining pinning for this ticket in pillars/workerconf.sls (there are for #136130 and #135407 which is expected) and none in job groups (note that GitLab can't search this repo, it needs to be cloned with subrepos).