Project

General

Profile

action #52286

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

[functional][y] automate scenario for yast2 dump YaST module on s390x

Added by riafarov over 2 years ago. Updated 5 months ago.

Status:
Blocked
Priority:
Normal
Assignee:
Target version:
Start date:
2019-05-29
Due date:
% Done:

0%

Estimated time:

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

History

#1 Updated by SLindoMansilla over 2 years ago

  • Category set to New test

As a result of backlog triaging (see https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging for more information).

Please, feel free to adjust the category or the "[label]" if you think different.

#2 Updated by riafarov over 2 years ago

  • Due date changed from 2019-07-23 to 2019-07-30

#3 Updated by riafarov over 2 years ago

  • Description updated (diff)
  • Due date deleted (2019-07-30)
  • Assignee set to riafarov

#5 Updated by riafarov over 2 years ago

  • Status changed from New to Blocked

With mentioned bugs seems that we can only do very limited testing of the modules. Let's see if we'll get any of those issues fixed before proceeding.

#6 Updated by riafarov over 2 years ago

  • Due date set to 2020-02-04
  • Target version changed from Milestone 27 to Milestone 29

#7 Updated by riafarov about 2 years ago

  • Target version changed from Milestone 29 to Milestone 30+

#8 Updated by mgriessmeier almost 2 years ago

  • Target version changed from Milestone 30+ to Milestone 30

bulk moved to M30 for revisiting

#9 Updated by riafarov almost 2 years ago

  • Due date changed from 2020-02-04 to 2020-04-07
  • Target version changed from Milestone 30 to Milestone 33

#10 Updated by riafarov over 1 year ago

  • Due date changed from 2020-04-07 to 2021-01-12
  • Target version changed from Milestone 33 to future

Unfortunately, we cannot expect the fix anytime soon.

#11 Updated by SLindoMansilla over 1 year ago

  • Due date deleted (2021-01-12)

#12 Updated by SLindoMansilla over 1 year ago

  • Due date set to 2021-01-12

#13 Updated by riafarov about 1 year ago

  • Project changed from openQA Tests to qe-yast
  • Due date deleted (2021-01-12)
  • Category deleted (New test)

#14 Updated by riafarov 10 months ago

  • Target version changed from future to SLE 15 SP3

#15 Updated by riafarov 7 months ago

  • Assignee changed from riafarov to oorlov

#16 Updated by oorlov 5 months ago

  • Target version changed from SLE 15 SP3 to Current

Also available in: Atom PDF