Project

General

Profile

Actions
Copy link

action #71008

closed

[opensuse][phub] vagrant: Tests fails to download asset file

Added by dimstar over 3 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
dancermak
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-09-05
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_vagrant@64bit fails in
tumbleweed

The test is supposedly getting a file using wget from the assets/other directory, but fails to do so.
wget terminates with errorcode 8, which, according the man page, means
8 Server issued an error response.

Test suite description

Maintainer: dancermak. Test vagrant, vagrant plugins and the vagrant boxes

Reproducible

Fails since (at least) Build 20200110

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by dancermak over 3 years ago

Actions
Copy link
 #2

Updated by SLindoMansilla over 3 years ago

  • Subject changed from vagrant: Tests fails to download asset file to [opensuse][phub] vagrant: Tests fails to download asset file
Actions
Copy link
 #3

Updated by okurz over 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: extra_tests_vagrant
https://openqa.opensuse.org/tests/1400463

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"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #4

Updated by okurz over 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: extra_tests_vagrant
https://openqa.opensuse.org/tests/1442461

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"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #5

Updated by dancermak over 3 years ago

I believe that this issue can be closed, as the current failures are related to VirtualBox behaving weirdly in nested virtualization environments.

Actions
Copy link
 #6

Updated by okurz over 3 years ago

  • Assignee set to dancermak

"Closing" this issue will not work. Did you see the comment in #71008#note-4 ? There are hints in there how to prevent reminder comments. As long as reviewers are using this ticket to label issues, e.g. https://openqa.opensuse.org/tests/1442461#comment-93473 by DimStar, someone is expecting someone else to fix the problems. So I guess you are a good candidate to solve this, hence assigning to you. Keep in mind that in openQA tests we are very flexible. You could implement a retry on multiple levels to ensure the test to work despite of temporary internal timeouts.

Actions
Copy link
 #7

Updated by okurz over 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: extra_tests_vagrant
https://openqa.opensuse.org/tests/1464038

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"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #8

Updated by okurz over 2 years ago

I came to this ticket due to periodically reviewing tickets as described on https://progress.opensuse.org/projects/openqatests/wiki#How-we-work-on-tickets

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives

First reminder: Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period).

Actions
Copy link
 #9

Updated by slo-gin over 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link
 #10

Updated by dimstar over 1 year ago

  • Status changed from New to Resolved

dancermak wrote:

I have also raised this issue here: https://github.com/os-autoinst/openqa-trigger-from-obs/issues/93

I'd agree with that - and since then, even those issues have been fixed and the tests passes (for now)

Actions
Copy link

Also available in: Atom PDF