Project

General

Profile

Actions

action #117340

closed

openQA-in-openQA test openqa_install+publish fails in start_test size:M

Added by tinita about 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2022-09-28
Due date:
2022-10-22
% Done:

0%

Estimated time:

Description

Observation

openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install+publish@64bit-2G fails in
start_test

Test suite description

Maintainer: okurz@suse.de Test for installation of openQA itself. To be used with "openqa" distri. Publishes an qcow2 image including the openQA installation ready to run as an appliance.

Reproducible

Fails since (at least) Build :TW.12329

Expected result

Last good: :TW.12328 (or more recent)

Further details

Always latest result in this scenario: latest

Suggestions

Actions #1

Updated by tinita about 2 years ago

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

Updated by tinita about 2 years ago

  • Category set to Regressions/Crashes
Actions #3

Updated by livdywan about 2 years ago

  • Subject changed from openQA-in-openQA test openqa_install+publish fails in start_test to openQA-in-openQA test openqa_install+publish fails in start_test size:M
  • Description updated (diff)
  • Status changed from New to Workable
Actions #4

Updated by mkittler almost 2 years ago

  • Assignee set to mkittler
Actions #5

Updated by mkittler almost 2 years ago

  • Status changed from Workable to In Progress

The use of OPENQA_CLI_RETRIES makes only a difference for 500 responses. So we should not be surprised that it doesn't help here.

Save the result in a variable to facilitate debugging

I'll create a PR.

Actions #6

Updated by mkittler almost 2 years ago

Actions #7

Updated by openqa_review almost 2 years ago

  • Due date set to 2022-10-22

Setting due date based on mean cycle time of SUSE QE Tools

Actions #8

Updated by mkittler almost 2 years ago

  • Status changed from In Progress to Feedback

The PR has been merged. I suppose now we just have to wait until the problem occurs again.

Actions #9

Updated by livdywan almost 2 years ago

  • Status changed from Feedback to Resolved

We don't know if this will or won't occur again, and we have a minimal improvement, hence resolving

Actions

Also available in: Atom PDF