action #151843
closedcoordination #151822: [epic] Soft-fails mitigation
Revisit soft-failure bsc#1204176
0%
Description
Motivation¶
See parent epic.
https://openqa.suse.de/tests/12933418#step/iscsi_client/60 -> bsc#1203004
Acceptance criteria¶
AC1: Revisit soft-failure bsc#1204176
Updated by JERiveraMoya about 1 year ago
- Copied to action #151846: Revisit soft-failure bsc#992113 added
Updated by JERiveraMoya about 1 year ago
- Tags changed from qe-yam-dec-sprint, qe-yam-jan-sprint to qe-yam-jan-sprint
Updated by tinawang123 about 1 year ago
- Status changed from Workable to In Progress
- Assignee set to tinawang123
Updated by JERiveraMoya about 1 year ago
- Copied to deleted (action #151846: Revisit soft-failure bsc#992113)
Updated by tinawang123 about 1 year ago
- Status changed from In Progress to Resolved
Removed softfail
and Verified: https://openqa.suse.de/tests/13193543#
Updated by JERiveraMoya about 1 year ago ยท Edited
which PR removed the problem? the problem is sporadic (needs more than 1 verification), should be showing now a info box instead of a softfailure afir (when it is reproduced if it is reproduced at that point now).
Updated by tinawang123 about 1 year ago
I removed the needle softfail.
The sporadic problem has been fixed by https://progress.opensuse.org/issues/152821
Updated by JERiveraMoya about 1 year ago
- Status changed from Resolved to Workable
- Assignee deleted (
tinawang123)
Ticket is not about the needle softfail (but seems that that also needs to be removed) but bug https://bugzilla.suse.com/show_bug.cgi?id=1204176.
Seems that we are dealing with that in another ticket. Let's keep it open at the end of the list to revisit when #152821 will be resolved.
Updated by JERiveraMoya about 1 year ago
- Related to action #152821: Fix refreshment issue for iscsi_client via apply workaround `apply_workaround_poo124652` added
Updated by JERiveraMoya about 1 year ago
That other ticket wasn't in the sprint properly label, that makes sense why the mess, sorry for that, please check with SM for future collisions of tickets.
Updated by JERiveraMoya about 1 year ago
- Status changed from Workable to Resolved
- Assignee set to tinawang123
Set as resolved as you also did the investigation, thanks!