Project

General

Profile

Actions

action #81146

closed

Fix validate_zfcp to not depend on fixed WWPN

Added by JERiveraMoya over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Target version:
SUSE QA - SLE 15 SP3
Start date:
2020-12-17
Due date:
% Done:

0%

Estimated time:

Description

Observation

openQA test in scenario sle-15-SP3-Online-s390x-zfcp@s390x-zfcp fails in
validate_zfcp

Comparing https://openqa.suse.de/tests/5188617#step/disk_activation/7 with https://openqa.suse.de/tests/5162986#step/disk_activation/6 we can see that WWPN is swap, which didn't happen during development of the module and for many builds after that.
Now is different every run, some time WWPN is related with /dev/sda and sometimes with /dev/sdb. We need to remove from test data this and keep similar functionality in the test. See https://openqa.suse.de/tests/5337796# vs https://openqa.suse.de/tests/5315094#step/disk_activation/7

So we can either soften wwpn check and use regex, or do not validate exact mapping of luns to /dev/sd[ab], but still validating that we got 2 devices and both of them were mapped properly.

Test suite description

Maintainer: mgriessmeier, okurz

Installation-only test configuring an s390x ZFCP storage.

Reproducible

Fails since (at least) Build 108.1

Expected result

Last good: 102.1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by okurz about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: zfcp@s390x-zfcp
https://openqa.suse.de/tests/5212080

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #2

Updated by okurz about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: zfcp@s390x-zfcp
https://openqa.suse.de/tests/5304805

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #3

Updated by JERiveraMoya about 3 years ago

  • Priority changed from Normal to High
Actions #4

Updated by JERiveraMoya about 3 years ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (Bugs in existing tests)
Actions #5

Updated by riafarov about 3 years ago

  • Description updated (diff)
  • Status changed from New to Workable
Actions #6

Updated by riafarov about 3 years ago

  • Assignee set to riafarov
Actions #7

Updated by riafarov about 3 years ago

  • Status changed from Workable to In Progress
Actions #8

Updated by riafarov about 3 years ago

  • Status changed from In Progress to Feedback
Actions #9

Updated by riafarov about 3 years ago

  • Status changed from Feedback to Closed
Actions #10

Updated by okurz about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: zfcp@s390x-zfcp
https://openqa.suse.de/tests/5461634

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #11

Updated by riafarov about 3 years ago

  • Status changed from Closed to In Progress
Actions #12

Updated by riafarov about 3 years ago

  • Status changed from In Progress to Feedback
Actions #14

Updated by riafarov about 3 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF