action #122794
Updated by JERiveraMoya over 1 year ago
#### Motivation We have [a couple of scenarios](https://openqa.suse.de/tests/overview?result=failed&result=incomplete&result=timeout_exceeded&arch=&flavor=&machine=&test=detect_yast2_failures&modules=&module_re=&distri=sle&version=15-SP5&build=64.1&groupid=129#) 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. group. 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 Change the logic of the YaST investigation logs, soft-failing for already filed bug instead and failing for new problems. **AC2**: Remove scenario in Full medium to detect yast2 failures (as most of the time shows exactly the same than the one Online)