Project

General

Profile

Actions

action #52286

closed

coordination #51665: [functional][y][s390][epic] Create new test suite for s390 specific yast modules

Automate scenario for yast2 dump YaST module on s390x

Added by riafarov about 5 years ago. Updated 6 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Target version:
-
Start date:
2019-05-29
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Yast2 dump module test proposal:

That module is a front-end for mkdump. 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, 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,
  • Later by command line as in bootloader (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.

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

Actions

Also available in: Atom PDF