Project

General

Profile

Actions

action #120714

closed

coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5

[Research 24h] Investigate test fails in iscsi_client with wrong exit code

Added by jgwang over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
Start date:
2022-11-18
Due date:
% Done:

0%

Estimated time:

Description

Motivation

openQA test in scenario sle-15-SP5-Online-x86_64-iscsi_client_normal_auth_backstore_hdd@64bit fails in
iscsi_client
Figure out why we get a wrong exit code after running "yast2 iscsi-client", but we expected the exitcode is 0.

Acceptance criteria

AC1: Investigate why the exit code is wrong after running "yast iscsi-client"
AC2: File a bug with findings if corresponds.

Additional information

Apparently nothing changes in test data, test code or even infrastructure.
Try to reproduce it locally with two VMs, also we could try with other product to see if it is really a product bug o not.


Related issues 1 (0 open1 closed)

Related to qe-yam - action #120831: [Research: 16h] Research recent iscsi failuresResolvedcoolgw2022-11-22

Actions
Actions #1

Updated by maritawerner over 1 year ago

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

Updated by JERiveraMoya over 1 year ago

  • Tags set to qe-yast-refinement
  • Subject changed from test fails in iscsi_client with wrong exit code to [Research 24h] Investigate test fails in iscsi_client with wrong exit code
  • Description updated (diff)
  • Priority changed from Normal to High
  • Target version set to Current
Actions #3

Updated by JERiveraMoya over 1 year ago

  • Related to action #120831: [Research: 16h] Research recent iscsi failures added
Actions #4

Updated by JERiveraMoya over 1 year ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable
Actions #6

Updated by coolgw over 1 year ago

  • Assignee set to coolgw
Actions #7

Updated by coolgw over 1 year ago

  • Status changed from Workable to In Progress
Actions #9

Updated by coolgw over 1 year ago

  • Status changed from In Progress to Resolved
Actions #10

Updated by JERiveraMoya over 1 year ago

  • Parent task set to #121876
Actions

Also available in: Atom PDF