Project

General

Profile

Actions
Copy link

action #154681

closed

coordination #151822: [epic] Soft-fails mitigation

Revisit soft-failure bsc#1219209

Added by zoecao 3 months ago. Updated 13 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
zoecao
Target version:
-
Start date:
2024-02-01
Due date:
% Done:

0%

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

Description

Motivation

Revisit [bsc#1219209]
https://openqa.suse.de/tests/13344591#step/journal_check/10

"bsc#1217773": {
        "description": "Unable to send container stderr message to parent Broken pipe",
        "products": {
            "sle-micro": ["5.4"]
        },
        "type": "bug"

Acceptance criteria

AC1: Revisit soft-failure bsc#1219209.

Actions
Copy link
 #1

Updated by JERiveraMoya 3 months ago

  • Tags set to qe-yam-mar-sprint
  • Description updated (diff)
  • Status changed from New to Workable
  • Parent task set to #151822
Actions
Copy link
 #2

Updated by JERiveraMoya 3 months ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by JERiveraMoya 3 months ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by JERiveraMoya 2 months ago

  • Subject changed from To trace SLEM bugs of bsc#1219218 and bsc#1219209 to To trace SLEM bugs of bsc#1219209
  • Description updated (diff)
Actions
Copy link
 #5

Updated by JERiveraMoya 2 months ago

  • Subject changed from To trace SLEM bugs of bsc#1219209 to Revisit soft-failure bsc#1219209
Actions
Copy link
 #6

Updated by zoecao about 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to zoecao
Actions
Copy link
 #8

Updated by JERiveraMoya about 2 months ago ยท Edited

The PR is not for resolving this ticket, from the bug seems that the developers cannot reproduce it.
Can you provide a way for the developer to reproduce it without openQA?
Is it really reproducible at the moment, I saw your verification where you add the soft-failure to the json and I don't see any soft-failure so it means that the problem disappeared...?

In case is not reproducible or testeable at this point, please set Status to New so we can revisit it in the future (you can still be assigned to the ticket due to you are most likely going to receive notification from the bug). This is our standard procedure, in that way we can have metrics from the resolved tickets in this epic and we don't need more than one ticket for the same thing.

Actions
Copy link
 #9

Updated by zoecao about 2 months ago

JERiveraMoya wrote in #note-8:

The PR is not for resolving this ticket, from the bug seems that the developers cannot reproduce it.
Can you provide a way for the developer to reproduce it without openQA?
Is it really reproducible at the moment, I saw your verification where you add the soft-failure to the json and I don't see any soft-failure so it means that the problem disappeared...?

In case is not reproducible or testeable at this point, please set Status to New so we can revisit it in the future (you can still be assigned to the ticket due to you are most likely going to receive notification from the bug). This is our standard procedure, in that way we can have metrics from the resolved tickets in this epic and we don't need more than one ticket for the same thing.

Yes, there's no soft-failure in VR, I'll take a look at whether it is still reproducible, thanks for your comment.

Actions
Copy link
 #10

Updated by zoecao about 2 months ago

  • Status changed from In Progress to New

Checked why the soft-failure is not recorded, and tried to reproduce the issue manually, while at last I found the issue is gone when I rerun (by cloning) it:
https://openqa.suse.de/tests/13762884#step/journal_check/11

Already leave comment to the bug report [bsc#1219209]. So I set the status to New and cancel the PR.

Actions
Copy link
 #11

Updated by JERiveraMoya about 1 month ago

  • Tags changed from qe-yam-mar-sprint to qe-yam-apr-sprint
Actions
Copy link
 #12

Updated by JERiveraMoya about 1 month ago

  • Status changed from New to Workable
Actions
Copy link
 #13

Updated by JERiveraMoya 13 days ago

  • Status changed from Workable to Resolved

I will set as resolved, seems that is not visible anymore softfail or even the fail.

Actions
Copy link

Also available in: Atom PDF