action #137408
Updated by okurz 9 months ago
## Motivation
s390x mainframe(s) are being moved to PRG2 with the help of IBM. We need to support the process and help to bring back any QE related LPARs or VMs on those mainframes to be able to use them as part of openQA.
## Acceptance criteria
* **AC1:** All s390x openQA tests on openqa.opensuse.org instances referenced in o3 workers so far, e.g. see openqa.opensuse.org/admin/workers/ or https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls are able usable after the move to successfully execute tests PRG2
## Suggestions
* Follow s390x mainframe related moving coordination as referenced in #100455#Important-documents
* Read #132152 Wait for Eng-Infra/mainframe-owners to inform us about what was done in the area availability of o3 the network and machines
* Update access details in https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls where necessary
* See last worker definitions in #134912-34 and crosscheck with , e.g. see openqa.opensuse.org/admin/workers/
* Ask in particular mgriessmeier+gschlotter for collaboration – if not the assignee themselves ;)
* Ensure we have access to machines manually as well as with verification openQA jobs, both for o3+osd
* Ensure we work with proper FQDNs where possible, not IPv4 mess :)
* React to any user reports about not working or missing s390x tests/VMs/LPARs, etc.
* the openqa.opensuse.org openQA machine setting for "s390x-zVM-vswitch-l2" has REPO_HOST=192.168.112.100 and other references to 192.168.112. This needs to be changed as soon as zVM instances are able to reach new-ariel internally, e.g. over FTP
* Inform users about the result
* Ensure that https://openqa.opensuse.org/group_overview/34 shows no obvious incompletes/fails/stuck jobs, currently no new build for some days
Back