action #93119
Updated by mgriessmeier almost 3 years ago
## Description ## ~~~ For your information, the Mainframe zEC12 which hosted our LPARs s390p7 (s390x-kvm-sle15), s390p8 (s390x-kvm-sle12) and s390p9 (former QAM) - needed to be shut down, as we will get a new Mainframe in the upcoming weeks. This won't have much impact as for now, as we have backup workers for s390x-kvm-sle12. for s390x-kvm-sle15 we don't have them, but as I'm aware of, the corresponding jobs have been modified to run on s390x-kvm-sle12. (if not, please do so, as s390-kvm-sle15 won't be functional as of now) In the upcoming days I will set up more workers on our other mainframe zEC13. For now if you see failing testcases on worker_class 's390x-kvm-sle12', a simple restart should work as it will be triggered on the zEC13 workers (s390zp18). ~~~ Additionally, it seems there are still stests running on worker_class 'zkvm' which refers to an old LPAR s390pb, this was also shutdown. so the second goal of this ticket is to get rid of this machine as well ## Tasks ## * ~~Create PR to disable workers running on LPAR s390p7 and s390p8~~ DONE by dzedro ( https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/318) * ~~Identify jobs running on worker_class 'zkvm' and move them to worker_class 's390x-kvm-sle12' to be scheduled on s390zp18~~ * ~~Create PR to disable workers running on LPAR s390pb~~ DONE by https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/320 * ~~Setup new LPAR on zEC13 to mitigate the loss of the workers running on the old and shut down LPARs on zEC12~~ DONE by https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/320 * ~~Monitor Monitor jobs on s390-kvm-sle12 to spot potential setup issues on s390zp19~~ s390zp19 running fine for 2 weeks now * Temporarily change s390-kvm-sle15 worker config to mirror s390-kvm-sle12 * Document new setup and remove all references to the old one * Provide additional resources for manual testing