Project

General

Profile

Actions

action #97766

closed

Adapt the order of activation for ZFCP with client for libyui-rest-api

Added by syrianidou_sofia over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
2021-08-31
Due date:
% Done:

0%

Estimated time:

Description

There are some changes in the order of multipath activation. According to yast team PR: https://github.com/yast/yast-installation/pull/974 device activation will occcur before probing.

The change has reached all products that use the client for activating devices (DASD, ZFCP, FCoE, iSCSI). https://bugzilla.suse.com/show_bug.cgi?id=1187220#c13

SLE-15-SP4 is still inheriting the package from SLE-15-SP3:Update, see https://build.suse.de/package/show/SUSE:SLE-15-SP4:GA/yast2-installation

The expected package yast2-installation 4.4.15 is in review, see https://build.suse.de/request/show/248874 but as it was failing it inherited the update.

Observation

openQA test in scenario sle-15-SP4-Online-s390x-zfcp@s390x-zfcp fails in
scc_registration

Test suite description

Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainer: QE Yast, mgriessmeier

Installation-only test configuring an s390x ZFCP storage.

Reproducible

Fails since (at least) Build 29.1 (current job)

Expected result

Last good: 26.1 (or more recent)

Further details

Always latest result in this scenario: latest

Suggestion

Fix this test using client for libyui-rest-api as much as possible.


Related issues 1 (0 open1 closed)

Related to qe-yam - action #98811: 15-SP3 QU1 test fails in validate_multipath - topology changedClosedgeor

Actions
Actions

Also available in: Atom PDF