Project

General

Profile

action #9674

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

Added by RBrownSUSE over 6 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
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)

Checklist

  • SLE

Related issues

Blocked by openQA Tests - action #12330: Upgrades on s390Resolved2016-12-16

Blocked by openQA Project - action #12922: hard-chained jobs running on same worker one after anotherResolved2016-07-28

Blocks openQA Tests - action #13216: [sles][functional][s390x] Run extratest on s390xResolved2017-03-02

History

#1 Updated by RBrownSUSE over 6 years ago

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

#2 Updated by okurz almost 6 years ago

#3 Updated by okurz almost 6 years ago

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

#4 Updated by okurz almost 6 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

#5 Updated by okurz almost 6 years ago

#6 Updated by okurz almost 6 years ago

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

#7 Updated by okurz over 5 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?

#8 Updated by mgriessmeier over 5 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

#9 Updated by okurz over 5 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

#10 Updated by mgriessmeier over 5 years ago

  • Subject changed from s390x - test an existing installation to [sles][functional][s390x] test an existing installation

#11 Updated by mgriessmeier almost 5 years ago

  • Assignee deleted (mgriessmeier)

released subticket, so I'll do for this - we should rethink about it with sle15

#12 Updated by okurz almost 5 years ago

  • Target version set to Milestone 11

#13 Updated by okurz over 4 years ago

turns out to be a pre-requisite for more scenarios than we envisioned, referenced with blocked/blocking.

#14 Updated by sebchlad over 4 years ago

okurz: Start date: 25/11/2015

:)

also the description is vague. Could we update the description please, so me, as the Product Owner, could figure what is to be done here?

#15 Updated by okurz over 4 years ago

  • Description updated (diff)

#16 Updated by okurz over 4 years ago

  • Due date set to 2017-11-08

#17 Updated by riafarov over 4 years ago

  • Checklist item changed from to [x] SLE

#18 Updated by riafarov over 4 years ago

  • Status changed from In Progress to Resolved

#19 Updated by okurz over 4 years ago

  • Assignee set to riafarov

Awesome!

Also available in: Atom PDF