Project

General

Profile

Actions
Copy link

action #96293

closed

openQA Tests - coordination #96302: [qe-core][QU] Quarterly update failures

Test fails in 'clone' module of QR job group

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

Status:
Closed
Priority:
High
Assignee:
JERiveraMoya
Target version:
Current
Start date:
2021-07-29
Due date:
% Done:

0%

Estimated time:

Description

Observation

openQA test in scenario sle-15-SP3-Online-QR-aarch64-qam-allpatterns+addons@aarch64 fails in
clone

Test suite description

All modules defined in SCC_ADDONS
#20201124: added chrony-pool-openSUSE due to 15SP1 QU5 failure https://openqa.suse.de/tests/5060854

Reproducible

Fails since (at least) Build 188.11

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by szarate over 2 years ago

  • Parent task set to #96302

Setting to parent task to have a common tracker

Actions
Copy link
 #2

Updated by oorlov over 2 years ago

  • Status changed from New to Feedback

Test never failed on regular build, but started failing on QEM. Nothing was changed in between though, except s390x machines.

It was too optimistic to call a command to clone autoyast profile with '0' timeout. So, increasing timeout helped to solve the issue.

Fixed in: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13005
VR: https://openqa.suse.de/tests/6618921

Actions
Copy link
 #3

Updated by oorlov over 2 years ago

  • Assignee set to oorlov
Actions
Copy link
 #4

Updated by oorlov over 2 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #5

Updated by openqa_review over 2 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: qam-allpatterns+addons
https://openqa.suse.de/tests/6837971

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
Copy link
 #6

Updated by tjyrinki_suse over 2 years ago

  • Project changed from openQA Tests to qe-yam
  • Subject changed from [qem] test fails in clone to [qe-yast][qem][qu] test fails in clone
  • Category deleted (Bugs in existing tests)
  • Status changed from Resolved to Workable

Reopening, since indeed it still seems to happen now that we have a new build:
https://openqa.suse.de/tests/6872038#step/clone/5
https://openqa.suse.de/tests/6872053#step/clone/1

Actions
Copy link
 #7

Updated by openqa_review over 2 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: qam-allpatterns+addons
https://openqa.suse.de/tests/6872053

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
Copy link
 #8

Updated by tjyrinki_suse over 2 years ago

New QU build, seems similar: https://openqa.suse.de/tests/7148179

Actions
Copy link
 #10

Updated by oorlov over 2 years ago

  • Status changed from Workable to In Progress
Actions
Copy link
 #11

Updated by openqa_review over 2 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: qam-allpatterns+addons
https://openqa.suse.de/tests/7295648

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 bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions
Copy link
 #12

Updated by oorlov over 2 years ago

  • Tags set to qe-yast-refinement
  • Subject changed from [qe-yast][qem][qu] test fails in clone to Test fails in 'clone' module of QR job group
  • Status changed from In Progress to New
  • Assignee deleted (oorlov)
  • Priority changed from Normal to High
  • Target version set to Current

Moved to refinement stack and bumped the priority, so that the ticket may be picked up as soon as possible and resolved by any team member.

Actions
Copy link
 #13

Updated by oorlov over 2 years ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable
Actions
Copy link
 #14

Updated by JERiveraMoya over 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to JERiveraMoya
Actions
Copy link
 #15

Updated by JERiveraMoya over 2 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #16

Updated by JERiveraMoya over 2 years ago

  • Status changed from Feedback to Closed
Actions
Copy link

Also available in: Atom PDF