Project

General

Profile

action #47102

[functional][y] soft-fail bsc#1092088 in logs_from_installation_system - but maybe not in *all* installation scenarios?

Added by okurz over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 23
Start date:
2018-12-21
Due date:
2019-02-26
% Done:

0%

Estimated time:
3.00 h
Difficulty:

Description

Motivation

After #45470 http://s.qa.suse.de/test-status-sle15 lists now many more soft-fails. This already confuses RMs to think that we do not have other issues to look at, see http://mailman.suse.de/mailman/private/qa-sle/2019-February/001232.html . Probably we should prevent this single, non-critical issue to show up in all installation scenario but limit to dedicated scenario(s).

Acceptance criteria

  • AC1: Other soft-fails show up on http://s.qa.suse.de/test-status-sle15 in installation-based scenarios again
  • AC2: bsc#1092088 is still reported in at least one scenario
  • AC3: We still have the text-based popups for errors detected in the YaST logs in case of any failure, e.g. unresolved dependencies (see #47102#note-3)

Related issues

Related to openQA Tests - action #47927: [sle][functional][y] test fails in logs_from_installation_system: remove from detection all warnings (3 == stderr)Rejected2019-02-15

Blocks openQA Tests - coordination #47192: [sle][functional][y][epic] some openQA tests in staging take more than 50 minutesResolved2019-02-062019-06-04

Copied from openQA Tests - action #45470: [functional][y] soft-fail bsc#1092088 in logs_from_installation_systemResolved2018-12-212019-02-12

History

#1 Updated by okurz over 2 years ago

  • Copied from action #45470: [functional][y] soft-fail bsc#1092088 in logs_from_installation_system added

#2 Updated by okurz over 2 years ago

  • Status changed from New to Workable

With the ACs this should be workable.

#3 Updated by riafarov over 2 years ago

  • Estimated time set to 3.00 h

We can enable parsing for single scenario which we already have and to still have hints during investigation, this mechanism should be called in case of failure.
For the successful installations we might completely skip this part and only upload logs.

#4 Updated by okurz over 2 years ago

  • Description updated (diff)

#5 Updated by riafarov over 2 years ago

  • Assignee set to riafarov

#6 Updated by riafarov over 2 years ago

  • Status changed from Workable to Feedback

#7 Updated by okurz over 2 years ago

  • Related to action #47927: [sle][functional][y] test fails in logs_from_installation_system: remove from detection all warnings (3 == stderr) added

#8 Updated by okurz over 2 years ago

  • Blocks coordination #47192: [sle][functional][y][epic] some openQA tests in staging take more than 50 minutes added

#9 Updated by riafarov over 2 years ago

  • Status changed from Feedback to Resolved

#10 Updated by okurz over 2 years ago

that looks good. I can see that many other bugs are referenced again as soft-fail. I could not find bsc#1092088 directly referenced because in detect_yast2_failures you referenced another bug about the missing icons as well, that's ok. I hope that force_soft_failure can help us to not need to actively review such cases in the future.

#11 Updated by riafarov over 2 years ago

okurz wrote:

that looks good. I can see that many other bugs are referenced again as soft-fail. I could not find bsc#1092088 directly referenced because in detect_yast2_failures you referenced another bug about the missing icons as well, that's ok. I hope that force_soft_failure can help us to not need to actively review such cases in the future.

I also was not sure if openqa_review script parses soft-failures from jobs which have failed, but it's still mentioned in the comment, so bug is visible for the failure itself.

Also available in: Atom PDF