action #12330
closed
Added by mgriessmeier almost 8 years ago.
Updated about 7 years ago.
Estimated time:
(Total: 0.00 h)
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¶
- Description updated (diff)
- Assignee changed from mgriessmeier to okurz
- Blocked by action #12922: hard-chained jobs running on same worker one after another added
- Blocks action #11922: [sle][functional][s390][yast][y][hard] Add AutoYaST tests for s390 added
- Blocks action #9674: [sles][functional][s390x] test an existing installation added
- Description updated (diff)
- Blocked by action #13156: os-autoinst: Add support to easily switch VERSION during a test run added
- Description updated (diff)
- Target version set to Milestone 5
Not currently working on this one, blocked by #12922 which should be done first, probably also by me, but not in this year ;-)
@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=?
you mean that START_AFTER will automatically pick the same worker? - Should be worth a try, yeah
- Blocked by deleted (action #12922: hard-chained jobs running on same worker one after another)
- Blocked by deleted (action #13156: os-autoinst: Add support to easily switch VERSION during a test run)
- 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.
@mgriessmeier: zVM SP2->SP3 works. Add explicit base version variable in main.pm to load proper needles for preparation job
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
cool, so are we done here? if only the subticket about zkvm could be resolved…
- Target version changed from Milestone 5 to Milestone 6
- Status changed from In Progress to Resolved
Also available in: Atom
PDF