action #39344
closedcoordination #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
[functional][y][s390] create new test suite for yast dump module
0%
Description
Motivation¶
After analysis of reported YaST bugs, there is one https://bugzilla.suse.com/show_bug.cgi?id=1040944 which fails in YaST dump module
Acceptance criteria¶
- Module is tested manually on s390
- There is simple test which verifies basic functionality of YaST dump module on s390
Suggestions¶
- Learn what module is for
- Test manually on zVM and zKVM
- Develop automated test scenario to verify functionality of the YaST module
- Enable at least on s390x ( but potentially on x86 if it applys to that arch as well).
Updated by okurz over 5 years ago
- Target version changed from Milestone 20 to Milestone 23
Updated by okurz about 5 years ago
- Due date changed from 2019-03-26 to 2019-04-30
- Target version changed from Milestone 23 to Milestone 24
later sprint due to limited capacity
Updated by riafarov about 5 years ago
- Due date changed from 2019-04-30 to 2019-05-21
Updated by riafarov almost 5 years ago
- Target version changed from Milestone 24 to Milestone 25
Updated by JERiveraMoya almost 5 years ago
- Description updated (diff)
- Status changed from New to Workable
- Estimated time set to 8.00 h
Updated by JRivrain almost 5 years ago
- Status changed from Workable to In Progress
Updated by JRivrain almost 5 years ago
This module is just a front-end for the mkdump perl script. It lists DASD or ZFCP devices (only the ones that can be used as dump device) and allows to initialize them, then exits. That's all.
It is the same as doing the following:
mkdump --list-dasd
mkdump --list-zfcp
mkdump [--force] /dev/[device]
except that the error output from mkdump is not always properly displayed.
Updated by JRivrain almost 5 years ago
Tested on zVM, for zKVM we need access to some of the dasd devices attached to the hypervisor. There are actually 268 offline dasd devices on s390p8, but I do not know if they can be used.
Not tested: zfcp devices, we don't seem to have any.
Updated by JRivrain almost 5 years ago
I have not advanced much on this ticket, I have mostly been doing manual testing on GMC2.
I reported a bug though https://bugzilla.suse.com/show_bug.cgi?id=1135241&GoAheadAndLogIn=1 : mkdump lists devices that it should not.
Updated by JRivrain almost 5 years ago
- Copied to coordination #51665: [functional][y][s390][epic] Create new test suite for s390 specific yast modules added
Updated by JRivrain almost 5 years ago
- Status changed from In Progress to Resolved
Created a new ticket as it does not make much sense to create an SUT only for that module.
Updated by JRivrain almost 5 years ago
- Status changed from Resolved to In Progress
re-opening, I thought we had no ZFCP devices to play with but we do.
Updated by JERiveraMoya almost 5 years ago
- Status changed from In Progress to Resolved
Proposal will be added to related ticket.
Updated by riafarov almost 5 years ago
- Copied to deleted (coordination #51665: [functional][y][s390][epic] Create new test suite for s390 specific yast modules)