Project

General

Profile

Actions
Copy link

action #158742

open

coordination #151822: [epic] Soft-fails mitigation

Revisit soft-failure bsc#1206132

Added by JERiveraMoya 3 months ago. Updated 3 days ago.

Status:
Workable
Priority:
Normal
Assignee:
hjluo
Target version:
-
Start date:
2024-04-10
Due date:
% Done:

0%

Estimated time:
Tags:
qe-yam-aug-sprint

Description

Motivation

See parent epic.
https://openqa.suse.de/tests/13989736#step/iscsi_client/45 -> bsc#1206132

Acceptance criteria

AC1: Revisit soft-failure bsc#1206132

Actions
Copy link
 #1

Updated by JERiveraMoya 3 months ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by JERiveraMoya 2 months ago

  • Tags changed from qe-yam-apr-sprint to qe-yam-may-sprint
Actions
Copy link
 #3

Updated by hjluo about 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions
Copy link
 #4

Updated by JERiveraMoya about 1 month ago

  • Tags changed from qe-yam-may-sprint to qe-yam-jan-sprint
Actions
Copy link
 #5

Updated by JERiveraMoya about 1 month ago

  • Tags changed from qe-yam-jan-sprint to qe-yam-jun-sprint
Actions
Copy link
 #6

Updated by JERiveraMoya 17 days ago

could you please update state here? thanks.

Actions
Copy link
 #7

Updated by hjluo 12 days ago ยท Edited

  • Now run on 15sp3 without workaroudn apply_workaround_bsc1206132() it still failed with yast2 iscsi-client' didn't finish or exited with non-zero.
    Test died: 'yast2 iscsi-client ' didn't finish or exited with non-zero code
  • Now asking Lee Duncan if it is expected or not for that product. (sent mail and wait for his reply)
Actions
Copy link
 #8

Updated by hjluo 11 days ago

Mail exchange:

Hi Lee,
We are now revisiting bugbsc#1206132
and found it still in sles15sp3 MU update builds. https://openqa.suse.de/tests/14654652
From https://bugzilla.suse.com/show_bug.cgi?id=1206132#c22 I found that we do not push open-iscsi fix to sles15sp3.
So my question is if this is expected or not for sles15sp3? do we have any plan to push this fix to sles15sp3 to make it work for our Yast MU testing?

Thanks a lot.

Lee Duncan replied with:

Please re-open the bug and request a port for SLE-15-SP3. That should
be no problem.

Actions
Copy link
 #9

Updated by hjluo 11 days ago

Actions
Copy link
 #10

Updated by JERiveraMoya 4 days ago

  • Tags changed from qe-yam-jun-sprint to qe-yam-jul-sprint
Actions
Copy link
 #11

Updated by hjluo 3 days ago

  • Now we're wait the dev for a port for SLE-15-SP3 which he agreed.
Actions
Copy link
 #12

Updated by JERiveraMoya 3 days ago

  • Tags changed from qe-yam-jul-sprint to qe-yam-aug-sprint
  • Status changed from In Progress to Workable

hjluo wrote in #note-11:

  • Now we're wait the dev for a port for SLE-15-SP3 which he agreed.

For informative purpose, please, write in the last message of the bug that you are requesting a port and you have agreed offline with developers about it (it is confusing to use so many tools, so we need to be clear for anyone reading the bug).
I'm moving to August sprint to revisit and keep you assigned.

Actions
Copy link

Also available in: Atom PDF