coordination #33862: [sles][functional][epic][s390x][yast][y] Review and extend test coverage of YaST2 modules on s390x - openQA Tests - openSUSE Project Management Tool

Actions

coordination #33862

closed

coordination #33859: [qe-core][sles][functional][saga][s390x] Review s390x Bugs found by IBM and see what can be implemented in the future

[sles][functional][epic][s390x][yast][y] Review and extend test coverage of YaST2 modules on s390x

Added by mgriessmeier about 6 years ago. Updated over 3 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

New test

Target version:

Start date:

2018-03-27

Due date:

% Done:

100%

Estimated time:

(Total: 10.00 h)

Difficulty:

Description

User Story¶

My feeling is that we don't have good coverage of (s390-specific) YaST-modules on s390x. This is about to get an overview of existing and an idea how to extend this coverage.

t.b.d

Further information¶

Enable yast2_ncurses testsuite on s390x ->
Error "Augeas parsing/serializing error: Failed to match" displayed during installation step "Saving network configuration" when VLAN is configured - (sles12.3)
Package yast2-cio is missing - (sles15 beta2)
Package yast2-cio not installed by default on s390x - (sles15 beta4)
DASD devices onlined via Yast2 are not persistant across reboot](https://bugzilla.suse.com/show_bug.cgi?id=707059) - (sles11.2)
"yast onpanic" dialog does not offer prepared zFCP dump devices - (sles12.3)
Exiting the "yast dump" dialog always displays an error (yast2-s390) - (sles12.3)

Subtasks 4 (0 open — 4 closed)

Actions

#1

Updated by okurz about 6 years ago

Subject changed from [sles][functional][epic][s390x] Review and extend test coverage of YaST2 modules on s390x to [sles][functional][epic][s390x][yast][y] Review and extend test coverage of YaST2 modules on s390x

Actions

#2

Updated by riafarov about 6 years ago

Due date changed from 2018-04-10 to 2018-04-24

due to changes in a related task

Actions

#3

Updated by okurz about 6 years ago

Due date changed from 2018-04-24 to 2018-06-05

due to changes in a related task

Actions

#4

Updated by riafarov almost 6 years ago

Due date changed from 2018-06-05 to 2018-07-03

due to changes in a related task

Actions

#5

Updated by okurz almost 6 years ago

Target version changed from Milestone 16 to Milestone 18

due to subtasks

Actions

#6

Updated by okurz almost 6 years ago

Target version changed from Milestone 18 to Milestone 18

Actions

#7

Updated by okurz almost 6 years ago

Target version changed from Milestone 18 to Milestone 21

Actions

#8

Updated by riafarov over 5 years ago

Due date changed from 2018-12-31 to 2019-01-29

due to changes in a related task

Actions

#9

Updated by okurz over 5 years ago

Status changed from New to Blocked
Assignee set to okurz
Target version changed from Milestone 21 to Milestone 24

waiting for #39344

Actions

#10

Updated by riafarov over 5 years ago

Due date changed from 2019-01-29 to 2019-03-12

due to changes in a related task

Actions

#11

Updated by okurz about 5 years ago

Due date changed from 2019-03-12 to 2019-03-26

due to changes in a related task

Actions

#12

Updated by okurz about 5 years ago

Due date changed from 2019-03-26 to 2019-04-30

due to changes in a related task

Actions

#13

Updated by okurz about 5 years ago

Target version changed from Milestone 24 to Milestone 25

to review post-absence

Actions

#14

Updated by okurz about 5 years ago

Assignee changed from okurz to mgriessmeier

@mgriessmeier to track as stand-in

Actions

#15

Updated by okurz about 5 years ago

Due date changed from 2019-04-30 to 2019-06-30

due to changes in a related task

Actions

#16

Updated by riafarov almost 5 years ago

Assignee changed from mgriessmeier to riafarov
Target version changed from Milestone 25 to Milestone 27

Taking over, it's not [u]

Actions

#17

Updated by riafarov almost 5 years ago

Due date changed from 2019-07-30 to 2019-06-30

due to changes in a related task

Actions

#18

Updated by riafarov almost 5 years ago

Due date changed from 2019-08-13 to 2019-08-27

due to changes in a related task

Actions

#19

Updated by riafarov almost 5 years ago

Due date changed from 2019-08-27 to 2019-09-24

due to changes in a related task

Actions

#20

Updated by riafarov over 4 years ago

Due date changed from 2019-09-24 to 2019-07-15

due to changes in a related task

Actions

#21

Updated by mgriessmeier over 4 years ago

Target version changed from Milestone 27 to Milestone 28

Actions

#22

Updated by riafarov over 4 years ago

Target version changed from Milestone 28 to Milestone 30+

Actions

#23

Updated by mgriessmeier over 4 years ago

Target version changed from Milestone 30+ to Milestone 30

bulk moved to M30 for revisiting

Actions

#24

Updated by SLindoMansilla about 4 years ago

Due date changed from 2021-01-12 to 2019-07-15

due to changes in a related task: #51665

Actions

#25

Updated by riafarov almost 4 years ago

Target version changed from Milestone 30 to future

Actions

#26

Updated by szarate over 3 years ago

Tracker changed from action to coordination
Status changed from Blocked to New

Actions

#27

Updated by szarate over 3 years ago

See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html

Actions

#28

Updated by riafarov over 3 years ago

Status changed from New to Resolved

We have outcome epic: #51665 so resolving this one and continuing in that epic.

Actions

Also available in: Atom PDF