action #9674: [sles][functional][s390x] test an existing installation - openQA Tests (public) - openSUSE Project Management Tool

Actions

Copy link

action #9674

closed

[sles][functional][s390x] test an existing installation

Added by RBrownSUSE over 9 years ago. Updated over 7 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

riafarov

Category:

New test

Target version:

openQA Project (public) - Milestone 11

Start date:

2015-11-25

Due date:

2017-11-08

% Done:

50%

Estimated time:

Difficulty:

Description

Goal¶

So we can schedule a whole bunch of tests based on an already installed machine

Acceptance criteria¶

AC1: Any "extra tests" is scheduled on any s390x, e.g. for "SLE 15 functional"

Suggestions¶

As zVM does not provide us with an image saving/loading feature we should go with s390x-kvm. Scheduling "extra_tests_filesystem" or "extra_tests_in_textmode" should be fine. I think we have them in the test development group already? (1-4h)

Hide closed

Checklist

Related issues 3 (0 open — 3 closed)

Actions

Copy link

Updated by RBrownSUSE about 9 years ago

Checklist item changed from to [ ] SLE
Target version deleted (~~156~~)

Actions

Copy link

Updated by okurz over 8 years ago

Blocked by action #12330: Upgrades on s390 added

Actions

Copy link

Updated by okurz over 8 years ago

Blocked by action #12922: hard-chained jobs running on same worker one after another added

Actions

Copy link

Updated by okurz over 8 years ago

okurz and mgriessmeier have a boot_s390.pm which is prerequisite but challenges left:

for zkvm we can rely on images (depends on #12330)
for zvm: how to ensure that an existing installation is there? probably depends on #12922

Actions

Copy link

Updated by okurz over 8 years ago

PR ready for "boot into existing system": https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1598

Actions

Copy link

Updated by okurz over 8 years ago

Blocks action #13216: [sles][functional][s390x] Run extratest on s390x added

Actions

Copy link

Updated by okurz about 8 years ago

as described in #12330 for zVM we just assume subsequent jobs to run on the same machine immediately as long as the worker class restricts the scenarios to run only on one so we are able to trigger tests on existing installations but only in serial execution. For zKVM we now have proper image handling so that spawning jobs based on images of existing installations should be feasible.

#13216 is a followup with a specific example, i.e. trigger extra tests on s390x.

@mgriessmeier: DONE?

Actions

Copy link

Updated by mgriessmeier about 8 years ago

working on it for zKVM at the moment
for zVM I plan to set up a new Worker_Class to also run console and extratests on it

Actions

Copy link

Updated by okurz about 8 years ago

I would say we have it already for zVM, too. The upgrade tests are using "an existing installation". But we can not close this ticket before the subtickets are done anyway

Actions

Copy link

#10