action #30892
closed
[opensuse][tools]multi-machine worker setup
Added by okurz almost 7 years ago.
Updated over 5 years ago.
Description
For various tests we have in SLE we can not schedule them in the o3 infrastructure because there are no multi-machine capable workers setup.
[25 Jan 2018 17:46:43] <okurz> coolo: do we have multimachine openQA workers in o3?
[25 Jan 2018 17:49:02] <coolo> okurz: I don't think so
[25 Jan 2018 17:49:15] <okurz> coolo: what can we do about it?
[25 Jan 2018 17:52:12] <coolo> okurz: openvswitch it
[25 Jan 2018 17:52:42] <okurz> coolo: would you really entrust me with this?
[25 Jan 2018 17:52:52] <coolo> no
[25 Jan 2018 17:53:06] <coolo> but me neither - I hate networks
[25 Jan 2018 17:53:21] <okurz> who can be trusted with this?
[25 Jan 2018 17:55:17] <coolo> okurz: try to convince rbrown?
[25 Jan 2018 17:56:05] <okurz> that would be sysrich ^^
[25 Jan 2018 17:56:28] <okurz> he should be a fan of multimachine tests so let's see :)
[25 Jan 2018 18:00:09] <coolo> okurz: indeed. he should be able to test kubik at some point :)
- Subject changed from [opensuse]multi-machine worker setup to [opensuse][tools]multi-machine worker setup
- Blocks coordination #9576: [epic][opensuse][sle][functional][y] VNC+SSH Installations added
- Blocks action #9900: [sle][functional][hard][opensuse][y] nis+autofs added
- Blocks action #12966: Enable iSCSI client/server test scenario for openSUSE added
- Blocks action #9502: [opensuse][sle][functional][u][hard]Salt multi-machine test added
- Related to action #31852: o3 does not support multimachine testing added
- Blocks action #31921: [kernel][network]Wicked fails the newly added dhcp test on o3 added
- Status changed from New to In Progress
- Assignee set to asmorodskyi
I am taking care about this , but with low prio ...
- Status changed from In Progress to Workable
- Assignee changed from asmorodskyi to okurz
Oli, for the time being I would prefer (as the person who takes care of HPC testing for SLE15) not to have Anton assigned to tasks by Oli.
@Anton let us talk about it in f2f conversation, after which we can update the ticket.
- Status changed from Workable to In Progress
- Assignee changed from okurz to asmorodskyi
as discussed there was a misunderstanding assuming that I assigned the ticket to asmorodskyi but I am just the author :)
- Blocks deleted (action #31921: [kernel][network]Wicked fails the newly added dhcp test on o3)
- Related to action #31921: [kernel][network]Wicked fails the newly added dhcp test on o3 added
I created first raw draft of expected salt recepie repository for o3 - https://gitlab.suse.de/asmorodskyi/o3-openqa-salt-review. Mainly it is copy/paste of osd salt/pillar repos with cutting all unrelated / too complex for first draft things. There is still a lot of thing to cut/modify but before going further I want to get early feedback if I am generally moving in a right direction
- Status changed from In Progress to Blocked
Additionally to comment above I sent an email to openqa@suse.de with request for feedback, so waiting for feedback before going further
@asmorodskyi I think in the mean time QA tools commited to take team responsibility for the o3 infrastructure. Maybe they are willing to support more here. WDYT?
@okurz I think the best "person" to answer about "what QA tools team willing to support " is "QA tools team " and @asmorodskyi is not a part of it ;)
- Blocks action #37045: [opensuse][functional][y] enable iscsi server/client scenario for openSUSE added
- Assignee deleted (
asmorodskyi)
Don't see the way for solving this ticket
- Related to coordination #38885: [functional][y][epic] Extend network related yast2 modules tests to be proper multimachine tests added
- Status changed from Blocked to Workable
Please don't keep tickets in blocked with no assignee. I do no think this is currently blocked but just needs to be worked on.
According to https://openqa.opensuse.org/admin/workers the worker machine openqaworker1 is configured with the "tap" worker class and should be multi-machine capable, probably manually configured by sysrich when he was setting up the workers as new transactional servers. One should try out if multi-machine jobs work now.
- Status changed from Workable to Resolved
- Assignee set to okurz
[28/05/2019 13:21:23] <okurz> asmorodskyi: am I right to assume that multi-machine on o3 is all-working?
[28/05/2019 13:21:37] <okurz> asmorodskyi: e.g. the wicked_basic_ref and wicked_basic_sut? https://openqa.opensuse.org/tests/943859
[28/05/2019 13:25:08] <asmorodskyi> okurz: yes it was working since sysrich set it up few months ago
[28/05/2019 13:28:10] <okurz> asmorodskyi: ok, cool. thx. It's limited to only some instances on openqaworker1 but I assume that's good enough for now
[28/05/2019 13:33:00] <okurz> asmorodskyi: what I don't understand, shouldn't the tests specify that they rely on "tap" workers or something?
[28/05/2019 13:34:37] <asmorodskyi> okurz: yes they do
[28/05/2019 13:37:36] <asmorodskyi> okurz: yes they should have NICTYPE=tap actually :\
[28/05/2019 13:39:20] <okurz> asmorodskyi: why does it work then? ;)
Also available in: Atom
PDF