Project

General

Profile

Actions
Copy link

action #33232

open

coordination #28630: [qe-core] setup for LPAR installation (manual + automatic)

coordination #28869: [epic] Automated installation on s390x LPAR through zHMC & integration into openQA

Execute useful LPAR installation testcases in the QE core job group

Added by mgriessmeier over 6 years ago. Updated 4 months ago.

Status:
Blocked
Priority:
Normal
Assignee:
mgriessmeier
Category:
-
Target version:
QA - future
Start date:
2020-01-02
Due date:
% Done:

0%

Estimated time:

Description

User story

Once the requirements for automated LPAR installation in openQA are done, we need to think about which testcases need to be executed in the functional job group

Acceptance criteria

  • AC1: Automated LPAR installation can be done in Functional job group
  • AC2: Useful tests are executed on LPAR on a regular base

Related issues 1 (1 open — 0 closed)

Follows openQA Project - action #33226: Add a simple testsuite which uses the planned LPAR backendBlockedmgriessmeier2020-01-01

Actions
Actions
Copy link
 #1

Updated by mgriessmeier over 6 years ago

  • Precedes action #33226: Add a simple testsuite which uses the planned LPAR backend added
Actions
Copy link
 #2

Updated by mgriessmeier over 6 years ago

  • Precedes deleted (action #33226: Add a simple testsuite which uses the planned LPAR backend)
Actions
Copy link
 #3

Updated by mgriessmeier over 6 years ago

  • Follows action #33226: Add a simple testsuite which uses the planned LPAR backend added
Actions
Copy link
 #4

Updated by mgriessmeier over 6 years ago

  • Due date changed from 2018-07-03 to 2018-05-22
  • Start date changed from 2018-05-23 to 2018-04-11

due to changes in a related task

Actions
Copy link
 #5

Updated by nicksinger over 6 years ago

  • Due date changed from 2018-05-22 to 2018-06-05
  • Start date changed from 2018-04-11 to 2018-04-25

due to changes in a related task

Actions
Copy link
 #6

Updated by nicksinger over 6 years ago

  • Follows deleted (action #33226: Add a simple testsuite which uses the planned LPAR backend)
Actions
Copy link
 #7

Updated by nicksinger over 6 years ago

  • Follows action #33226: Add a simple testsuite which uses the planned LPAR backend added
Actions
Copy link
 #8

Updated by nicksinger over 6 years ago

  • Due date changed from 2018-06-05 to 2018-06-19
  • Start date changed from 2018-04-25 to 2018-05-09

due to changes in a related task

Actions
Copy link
 #9

Updated by nicksinger over 6 years ago

  • Due date changed from 2018-06-19 to 2018-06-05
  • Start date changed from 2018-05-09 to 2018-04-25

due to changes in a related task

Actions
Copy link
 #10

Updated by nicksinger over 6 years ago

  • Due date changed from 2018-06-05 to 2018-05-08
  • Target version changed from Milestone 15 to Milestone 16
Actions
Copy link
 #11

Updated by okurz over 6 years ago

  • Due date changed from 2018-05-08 to 2018-05-22
  • Start date changed from 2018-04-25 to 2018-05-09

due to changes in a related task

Actions
Copy link
 #12

Updated by mgriessmeier over 6 years ago

  • Due date changed from 2018-05-22 to 2018-06-05
  • Start date changed from 2018-05-09 to 2018-05-23

due to changes in a related task

Actions
Copy link
 #13

Updated by okurz over 6 years ago

  • Due date changed from 2018-06-05 to 2018-07-03
  • Start date changed from 2018-05-23 to 2018-06-20

due to changes in a related task

Actions
Copy link
 #14

Updated by okurz over 6 years ago

  • Target version changed from Milestone 16 to Milestone 17

S20 is M17

Actions
Copy link
 #15

Updated by okurz over 6 years ago

  • Due date changed from 2018-07-03 to 2018-06-20
  • Start date changed from 2018-06-20 to 2018-06-07

due to changes in a related task

Actions
Copy link
 #16

Updated by okurz over 6 years ago

  • Due date changed from 2018-06-20 to 2018-07-03
  • Start date changed from 2018-06-07 to 2018-06-20

due to changes in a related task

Actions
Copy link
 #17

Updated by mgriessmeier over 6 years ago

  • Due date changed from 2018-07-03 to 2018-07-31
  • Start date changed from 2018-06-20 to 2018-07-18

due to changes in a related task

Actions
Copy link
 #18

Updated by okurz over 6 years ago

  • Due date changed from 2018-07-31 to 2018-08-14
  • Start date changed from 2018-07-18 to 2018-08-01

due to changes in a related task

Actions
Copy link
 #19

Updated by okurz over 6 years ago

  • Target version changed from Milestone 17 to Milestone 18

it's M18 actually

Actions
Copy link
 #20

Updated by riafarov over 6 years ago

  • Due date changed from 2018-08-14 to 2018-09-11
  • Start date changed from 2018-08-01 to 2018-08-29

due to changes in a related task

Actions
Copy link
 #21

Updated by okurz over 6 years ago

  • Target version changed from Milestone 18 to Milestone 19

that's actually M19

Actions
Copy link
 #22

Updated by okurz over 6 years ago

  • Due date changed from 2018-09-11 to 2018-11-20
  • Start date changed from 2018-08-29 to 2018-11-07

due to changes in a related task

Actions
Copy link
 #23

Updated by okurz about 6 years ago

  • Target version changed from Milestone 19 to Milestone 20
Actions
Copy link
 #24

Updated by mgriessmeier about 6 years ago

  • Due date changed from 2018-11-20 to 2018-04-11
  • Start date changed from 2018-11-07 to 2018-03-29

due to changes in a related task

Actions
Copy link
 #25

Updated by okurz almost 6 years ago

  • Due date changed from 2018-11-20 to 2018-11-07
  • Start date changed from 2018-11-07 to 2018-10-25

due to changes in a related task

Actions
Copy link
 #26

Updated by okurz almost 6 years ago

  • Due date deleted (2018-11-07)
  • Target version changed from Milestone 20 to future
  • Start date changed from 2018-10-25 to 2018-11-07
Actions
Copy link
 #27

Updated by okurz over 5 years ago

  • Start date changed from 2018-11-07 to 2020-01-02

due to changes in a related task

Actions
Copy link
 #28

Updated by mgriessmeier over 4 years ago

  • Assignee set to mgriessmeier

to be done within this FY (until November)

Actions
Copy link
 #29

Updated by SLindoMansilla over 4 years ago

  • Subject changed from [sle][functional][virtualization][s390-kvm][s390x][tools][u] Execute useful LPAR installation testcases in the SLE Functional job group to [sle][functional][virtualization][s390-kvm][s390x][tools] Execute useful LPAR installation testcases in the SLE Functional job group
Actions
Copy link
 #30

Updated by okurz about 4 years ago

  • Subject changed from [sle][functional][virtualization][s390-kvm][s390x][tools] Execute useful LPAR installation testcases in the SLE Functional job group to [sle][functional][virtualization][s390-kvm][s390x] Execute useful LPAR installation testcases in the SLE Functional job group

I don't see the need for the SUSE QA Tools team (which ignored that issue so far anyway) so far. I am sure you will be able to find us in case of specific backend problems where you need support :)

Actions
Copy link
 #31

Updated by mgriessmeier 4 months ago

  • Subject changed from [sle][functional][virtualization][s390-kvm][s390x] Execute useful LPAR installation testcases in the SLE Functional job group to Execute useful LPAR installation testcases in the QE core job group
  • Status changed from New to Blocked

(updated subject)

Actions
Copy link

Also available in: Atom PDF