Project

General

Profile

Actions

action #91500

closed

Bump timeout in addon_products_sle

Added by JERiveraMoya about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Target version:
SUSE QA - SLE 15 SP3
Start date:
2021-04-21
Due date:
% Done:

0%

Estimated time:

Description

Observation

openQA test in scenario sle-15-SP3-Full-x86_64-select_modules_and_patterns+registration@svirt-hyperv fails in
addon_products_sle

Test suite description

Full Medium installation that covers the following cases:
1. Additional modules enabled using SCC (Legacy, Development Tools,
Web and Scripting, Containers, Desktop Applications);
2. Yast patterns installed;
3. System registration is skipped during installation;
4. Installation is validated by successful boot and that YaST does not
report any issues;
5. Registration is performed on the installed system.

We could try to bump timeout as it seems that after failure reaches the screen. Also, take a look to previous runs, because this scenario had previous instabilities.

Actions #1

Updated by JERiveraMoya about 3 years ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (Bugs in existing tests)
Actions #2

Updated by oorlov almost 3 years ago

  • Status changed from New to Workable
Actions #3

Updated by syrianidou_sofia almost 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to syrianidou_sofia
Actions #4

Updated by syrianidou_sofia almost 3 years ago

  • Status changed from In Progress to Resolved
Actions #5

Updated by JERiveraMoya almost 3 years ago

  • Status changed from Resolved to Closed

let's use 'Closed' instead of 'Resolved' in order to track the tickets in our Kamban dashboard.

Actions #6

Updated by okurz almost 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: select_modules_and_patterns+registration@svirt-hyperv
https://openqa.suse.de/tests/5978893

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed
Actions

Also available in: Atom PDF