https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842016-10-11T02:44:09ZopenSUSE Project Management ToolopenQA Project - action #13972: openqa scheduler can not schedule the multi-machine job with different "WORKER_CLASS" in same grouphttps://progress.opensuse.org/issues/13972?journal_id=297142016-10-11T02:44:09Zjerrytangjtang@suse.com
<ul></ul><p>I think no one require 2 ipmi-phy-machines to perform the multi-machine job.<br>
This block the virtualization migration test (which require 2 machines)</p>
openQA Project - action #13972: openqa scheduler can not schedule the multi-machine job with different "WORKER_CLASS" in same grouphttps://progress.opensuse.org/issues/13972?journal_id=297242016-10-11T05:43:42Zxlaixlai@suse.com
<ul><li><strong>Assignee</strong> set to <i>coolo</i></li></ul> openQA Project - action #13972: openqa scheduler can not schedule the multi-machine job with different "WORKER_CLASS" in same grouphttps://progress.opensuse.org/issues/13972?journal_id=297262016-10-11T06:03:58Zxlaixlai@suse.com
<ul></ul><p>Clarify: Why need two different WORKER_CLASS?</p>
<p>For this dependency job group, one is source host, the other is destination host. The testsuite that needs to be run on the source host, needs to know the destination host ip. Only after scheduling, can we know which worker(IPMI_HOST) is the destination. mmapi has api to get parent job configurations. But the mmapi can neither get the static configurations of the worker(set in /etc/worker.ini), nor vars that are set dynamically after test starts. So we have no way to know the destination host ip via mmapi.<br>
We figure our another way: bind source testsuite to worker with source_worker_class, and destination testsuite to worker with dest_worker_class in job group. So we can statically know the destination host information.</p>
<p>However from experiment result, when bind the two dependency jobs to the two different kinds of worker separately, trigger child job , only this child job is triggered, parent is not. But if bind the two jobs to the same worker class, either the dest_worker_class or source_worker_class, the chain(child and parent) can be triggered.</p>
openQA Project - action #13972: openqa scheduler can not schedule the multi-machine job with different "WORKER_CLASS" in same grouphttps://progress.opensuse.org/issues/13972?journal_id=299822016-10-16T14:46:47Zcoolocoolo@suse.com
<ul><li><strong>Assignee</strong> changed from <i>coolo</i> to <i>nadvornik</i></li></ul> openQA Project - action #13972: openqa scheduler can not schedule the multi-machine job with different "WORKER_CLASS" in same grouphttps://progress.opensuse.org/issues/13972?journal_id=305762016-10-25T14:07:46Znadvorniknadvornik@suse.com
<ul></ul><p>I can't reproduce this.</p>
<p>Are you sure you have correct WORKER_CLASS on workers and jobs?</p>
openQA Project - action #13972: openqa scheduler can not schedule the multi-machine job with different "WORKER_CLASS" in same grouphttps://progress.opensuse.org/issues/13972?journal_id=311922016-11-08T22:46:50Zokurzokurz@suse.com
<ul><li><strong>Project</strong> changed from <i>openQA Tests</i> to <i>openQA Project</i></li></ul> openQA Project - action #13972: openqa scheduler can not schedule the multi-machine job with different "WORKER_CLASS" in same grouphttps://progress.opensuse.org/issues/13972?journal_id=364842017-01-17T16:57:14Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>Feature requests</i></li></ul> openQA Project - action #13972: openqa scheduler can not schedule the multi-machine job with different "WORKER_CLASS" in same grouphttps://progress.opensuse.org/issues/13972?journal_id=365322017-01-17T17:04:36Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>no reaction from author</p>
openQA Project - action #13972: openqa scheduler can not schedule the multi-machine job with different "WORKER_CLASS" in same grouphttps://progress.opensuse.org/issues/13972?journal_id=365342017-01-17T17:04:46Zokurzokurz@suse.com
<ul><li><strong>Category</strong> changed from <i>Feature requests</i> to <i>Support</i></li></ul>