action #52286
Updated by riafarov almost 5 years ago
Yast2 dump module test proposal:
--------------------------------
That module is a front-end for [mkdump](https://build.opensuse.org/package/view_file/Base:System/s390-tools/mkdump.pl?expand=1). It does this:
mkdump --list-dasd
mkdump --list-zfcp
mkdump [--force] /dev/[device]
Te mkdump modules automatically lists DASD or ZFCP device that can be used as dump device. Such device should be of ECKD type (mkdump [does not work with FBA](https://bugzilla.suse.com/show_bug.cgi?id=1135241), this can be subject to a soft failure) it must have exclusive access and have VM's RAM+ 10MB of free space.
## Acceptance criteria
1. Smoke test for yast2 dump module is enabled on s390x at least for SLE 15 SP2
## Suggestions
**1 - Activate some DASD and/or ZFCP device:**
This can be done in various ways:
* During [installation](https://openqa.suse.de/tests/2895489/modules/disk_activation/steps/1/src),
* Later by command line as in [bootloader](https://openqa.suse.de/tests/2895706#step/bootloader_s390/35) (command: "dasd_configure 0.0.200 1". That disk should be free is is "dumpable".)
* By putting this test module after the ones for dasd and/or zfcp, which also allow to enable disks.
See also: the SUT for ZFCP, [s390x-zfcp](https://openqa.suse.de/tests/2895872).
**2 - Start yast2 dump, initialize some disk for dumping.**
Don't forget to signal https://bugzilla.suse.com/show_bug.cgi?id=1135241 as soft-failure if an incompatible disk is shown here.
**3 - check if disk is marked as dump disk**, either in the module itself or with mkdump --list-dump
Documentation:
About dump devices : https://public.dhe.ibm.com/software/dw/linux390/docu/ljs0dt00.pdf
ZFCP and multipath tutorial (very good): https://share.confex.com/share/117/webprogram/Handout/Session9478/SHARE%20Boston%209222%20-%20SCSI.pdf