action #33865
closed
coordination #33859: [qe-core][sles][functional][saga][s390x] Review s390x Bugs found by IBM and see what can be implemented in the future
coordination #33862: [sles][functional][epic][s390x][yast][y] Review and extend test coverage of YaST2 modules on s390x
[sles][functional][s390x][easy][y] Enable yast2_ncurses testsuite for s390x
Added by mgriessmeier about 6 years ago.
Updated about 4 years ago.
Target version:
SUSE QA - Milestone 18
Description
User story¶
we want to check how yast modules behave on s390x
Acceptance Criteria¶
AC1: yast2_ncurses testsuite is running on o.s.d in functional
Tasks¶
- yast2_ncurses testsuite is running on o.s.d in test-development job group on a regular base to gather statistics how stable test is
- if stable enough, move to functional, if not create new tickets accordingly
- Evaluate business value, if used by any of the customers, if yes which modules exactly
- Subject changed from [sles][functional][s390x][easy] Enable yast2_ncurses testsuite for s390x to [sles][functional][s390x][easy][yast][y] Enable yast2_ncurses testsuite for s390x
- Subject changed from [sles][functional][s390x][easy][yast][y] Enable yast2_ncurses testsuite for s390x to [sles][functional][s390x][easy][y] Enable yast2_ncurses testsuite for s390x
- Description updated (diff)
- Status changed from New to Workable
- Due date changed from 2018-04-10 to 2018-04-24
- Due date changed from 2018-04-24 to 2018-06-05
- Target version changed from Milestone 15 to Milestone 16
not enough capacity in S15-S17. We think it's easy but new test can always have an impact on other stuff. So "easy" but not "trivial".
- Status changed from Workable to In Progress
- Assignee set to okurz
Triggered once to check feasibility
$ openqa_clone_job_osd --skip-chained-deps 1650904 TEST=yast2_ncurses Y2UITEST_NCURSES=1 EXTRATEST= _GROUP=0
-> https://openqa.suse.de/tests/1656222
- Blocked by action #34003: [tools] Better logging and error handling in case of remote console connections in consoles or backends, e.g. ssh added
- Status changed from In Progress to Blocked
- Due date changed from 2018-06-05 to 2018-07-03
- Target version changed from Milestone 16 to Milestone 17
Do not expect to get unblocked in S19, moving to S20
- Status changed from Blocked to Workable
- Status changed from Workable to In Progress
- Blocked by action #33202: [sle][functional][s390x][zkvm][u][hard] test fails in boot_to_desktop - still insufficient error reporting, black screen with mouse cursor - we all hate it (was: I hate it) added
- Status changed from In Progress to Blocked
- Target version changed from Milestone 17 to Milestone 17
- Estimated time set to 2.00 h
- Due date changed from 2018-07-03 to 2018-08-14
- Target version changed from Milestone 17 to Milestone 18
- Description updated (diff)
- Status changed from Blocked to Workable
- Assignee deleted (
okurz)
blockers are resolved afaics, so let's put this back to workable
- Status changed from Workable to In Progress
- Assignee set to riafarov
- Copied to coordination #39329: [sles][functional][s390x][y][epic] FIx yast2_ncurses testsuite for s390x added
- Status changed from In Progress to Resolved
So, as for business value, I've used bugzilla and http://houtsapps01.us.netiq.corp/siebelmatic2/?page=team&searchterm=12 support ticket system to identify used modules.
We are missing a lot of information about product usage, but what I was able to identify is that 'yast dump' YaST module is used on s390x. Majority of issues address installation, so it seems that servers are rarely configured manually or there are no issues with tooling on s390, or everything is configured without YaST modules.
- Due date deleted (
2018-08-14)
Also available in: Atom
PDF