action #32191
closed
[sle][migration][sle15] migrate s390x upgrade test cases to suse kvm(s390-kvm-sle12)
Added by dehai about 6 years ago.
Updated about 6 years ago.
Description
Status¶
Fow now, we use zkvm backend on s390x upgrade test cases
Change¶
migrate s390x upgrade test cases to suse kvm(s390-kvm-sle12)
Why¶
We've had a major breakdown of our mainframe storage backend - this means that all LPARs and z/VM guests are not available at the moment
This affects:
- s390p7, s390p8 (SUSE-KVM LPARs)
- s390pb (zKVM LPAR)
- zvm54.suse.de (z/VM guests)
# To Do
- Create original HDD images with suse kvm(s390-kvm-sle12)
- Change machine to s390-kvm-sle12
- Assignee changed from dehai to qmsu
- % Done changed from 0 to 80
Based on the priority of migration testing on different s390x guests (zVM > SUSE KVM > zKVM), I have switched most existing openQA migration tests for s390x from zKVM to SUSE KVM.
For SLE 15 migration daily job group: https://openqa.suse.de/group_overview/111
* All migration tests based on media and proxyscc have been switched to SUSE KVM (with exceptions bellow)
* Following basic migration tests will be run on both SUSE KVM and zKVM:
- media_upgrade_sles12sp3_workaround_modules
- proxyscc_upgrade_sles12sp3_allpatterns
For SLE 15 migration milestone job group: https://openqa.suse.de/group_overview/145
* All migration tests based on media will be kept on zKVM (considered that same build has been tested on SUSE KVM in daily job group)
* All migration tests based on scc have been switched to SUSE KVM (with exceptions bellow)
* Following basic migration tests with scc will be run on both SUSE KVM and zKVM:
* scc_upgrade_sles12sp3
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
Also available in: Atom
PDF