action #71008
closed
[opensuse][phub] vagrant: Tests fails to download asset file
Added by dimstar over 3 years ago.
Updated over 1 year ago.
Category:
Bugs in existing tests
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
- Subject changed from vagrant: Tests fails to download asset file to [opensuse][phub] vagrant: Tests fails to download asset file
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
I believe that this issue can be closed, as the current failures are related to VirtualBox behaving weirdly in nested virtualization environments.
- 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.
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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.
- Status changed from New to Resolved
Also available in: Atom
PDF