action #154681
closedcoordination #151822: [epic] Soft-fails mitigation
Revisit soft-failure bsc#1219209
0%
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.
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
Updated by JERiveraMoya 3 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)
Updated by JERiveraMoya 3 months ago
- Subject changed from To trace SLEM bugs of bsc#1219209 to Revisit soft-failure bsc#1219209
Updated by zoecao 2 months ago
Submit a PR for this ticket:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18785
VR: https://openqa.suse.de/tests/13684902#step/journal_check/10
Updated by JERiveraMoya 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.
Updated by zoecao 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.
Updated by zoecao 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.
Updated by JERiveraMoya about 2 months ago
- Tags changed from qe-yam-mar-sprint to qe-yam-apr-sprint
Updated by JERiveraMoya 29 days ago
- Status changed from Workable to Resolved
I will set as resolved, seems that is not visible anymore softfail or even the fail.