action #12330
closedopenQA Project - action #9680: libvirt backend
action #10204: zKVM Tests
Upgrades on s390
100%
Description
Implement upgrade tests on s390 (zKVM + zVM)
current state¶
- zKVM: #15536
- zVM: We added a "preparation" job which installs an older version of SLES and then a new job with START_AFTER is triggered on a special WORKER_CLASS so that the upgrade job will be triggered on the same host. As long as no other job interfers we can follow this approach. Validation run of offline migration on s390x zVM from SLES 12SP2 to SLES 12SP3: https://openqa.suse.de/tests/745154
tasks¶
- need to check with ihno first
- fix shutdown on zVM
- zkvm: Common NFS share also mounted on s390pb r/w We don't need that, using copy instead
- okurz: check with oholecek the status of multiple modules in tests-detailsview
old state as of 2016-12¶
- zkvm problem with nfs share, we would need a common share for s390pb as for the workers to read images from and for reupload -> I think we share the NFS there as well somehow or upload images and such
- zVM: see https://github.com/okurz/os-autoinst-distri-opensuse/tree/feature/s390_install_and_upgrade, needs either #12922 or install_previous_and_upgrade in one test_suite -> 2017-01: new approach, just assign special worker class with two jobs and START_AFTER
Updated by okurz over 7 years ago
- Description updated (diff)
- Assignee changed from mgriessmeier to okurz
Updated by okurz over 7 years ago
- Blocked by action #12922: hard-chained jobs running on same worker one after another added
Updated by okurz over 7 years ago
- Blocks action #11922: [sle][functional][s390][yast][y][hard] Add AutoYaST tests for s390 added
Updated by okurz over 7 years ago
- Blocks action #9674: [sles][functional][s390x] test an existing installation added
Updated by okurz over 7 years ago
http://lord.arch/tests/2616 is a first successful run of "install previous and upgrade". The screenshots are incomplete after the last step when doing the upgrade but the video is complete: http://lord.arch/tests/2616/file/video.ogv Enjoy a full installation of SLES 12 SP1 with following upgrade to SLES 12 SP2 :-)
Updated by okurz over 7 years ago
proof of concept PR for test code: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1684 , needles: https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/179
Updated by okurz over 7 years ago
- Blocked by action #13156: os-autoinst: Add support to easily switch VERSION during a test run added
Updated by mgriessmeier over 7 years ago
- Description updated (diff)
Update for zkvm:
opened PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2196
started to create some images and added migration jobs to Test-Development to see if it's working when PR got merged
Updated by okurz over 7 years ago
- Assignee deleted (
okurz)
Not currently working on this one, blocked by #12922 which should be done first, probably also by me, but not in this year ;-)
Updated by okurz about 7 years ago
@mgriessmeier: I did not yet review or fully understand the scheduling part of openQA but I think we never tried this: Can you just try to schedule two consecutive jobs: One SLE12SP2 installation job and one upgrade job with START_AFTER=?
Updated by mgriessmeier about 7 years ago
you mean that START_AFTER will automatically pick the same worker? - Should be worth a try, yeah
Updated by okurz about 7 years ago
- Blocked by deleted (action #12922: hard-chained jobs running on same worker one after another)
Updated by okurz about 7 years ago
- Blocked by deleted (action #13156: os-autoinst: Add support to easily switch VERSION during a test run)
Updated by okurz about 7 years ago
- Description updated (diff)
- Assignee set to okurz
Our approach following this seems to have worked.
special worker class "s390x-zVM-Upgrade" was added to worker config
@mgriessmeier moved the corresponding migration jobs already to the Migration: Server job group.
For now we only have this one offline migration scenario. Adding more should be possible considering the capacity of s390x workers but is of course limited. If necessary, work can be parallelized more by adding more special worker classes, e.g. one for SP1->SP3 upgrade, one for SP2->SP3 upgrade and such.
Ticket is now blocked by subtask #15536 only.
Updated by okurz about 7 years ago
@mgriessmeier: zVM SP2->SP3 works. Add explicit base version variable in main.pm to load proper needles for preparation job
Updated by mgriessmeier about 7 years ago
SP1->SP3 also works without code changes
there was only one needle which was outdated and needed to be modified for the preparation job
see passed test here: https://openqa.suse.de/tests/780474
I've already moved them to the migration group
Updated by okurz@suse.de about 7 years ago
cool, so are we done here? if only the subticket about zkvm could be resolved…
Updated by okurz about 7 years ago
- Target version changed from Milestone 5 to Milestone 6
Updated by mgriessmeier about 7 years ago
- Status changed from In Progress to Resolved
subticket for zkvm (https://progress.opensuse.org/issues/15536) is resolved
so everything should be done here -> closing