action #122794
closedcoordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Add yast log error 'Invalid path .value."eth0".NAME' as known error
0%
Description
Motivation¶
We have a couple of scenarios detecting yast failures in logs, once a new failure appear we agreed a time ago with YaST developers to file a bug to track it, but it is not really necessary to show a failure in YaST group, we have a way in current implementation to add known errors with regex.
Also it seems not be needed to run this scenario in Full and in Online Medium, with Online should suffice.
https://openqa.suse.de/tests/10220417#step/detect_yast2_failures/571
Acceptance criteria¶
AC1: Add yast log error 'Invalid path .value."eth0".NAME' as known error
AC2: Remove scenario in Full medium to detect yast2 failures (as most of the time shows exactly the same than the one Online)
Updated by JERiveraMoya over 1 year ago
- Subject changed from Make soft-fail test suite which investigate YaST logs for existing filed bugs to Add yast log error 'Invalid path .value."eth0".NAME' as known error
- Description updated (diff)
Updated by syrianidou_sofia over 1 year ago
- Status changed from Workable to In Progress
- Assignee set to syrianidou_sofia
Updated by syrianidou_sofia about 1 year ago
Added the error to known error in lib/opensusebasetest.pm , where module detect_yast2_failures functions are and moved the test suite to development job group, because there are new error messages that cause the test to fail.
https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/463
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16277/
Updated by JERiveraMoya about 1 year ago
we moved the scenario to dev group, that also should help (but we need to be diligent to review it often).
Updated by syrianidou_sofia about 1 year ago
- Status changed from In Progress to Resolved