action #60296
closed
[functional][u] test fails in qemu: Network issue on SUT: can't resolve openqa.suse.de
Added by dheidler over 4 years ago.
Updated over 4 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Description
Observation¶
openQA test in scenario sle-15-SP2-Online-aarch64-qemu@aarch64 fails in
qemu
Test suite description¶
Maintainer: dheidler@suse.de - Test QEMU and KVM
Reproducible¶
Fails since (at least) Build 93.1
Expected result¶
Last good: 92.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Suggestions¶
- Subject changed from test fails in qemu: Network issue on SUT: can't resolve openqa.suse.de to [functional][u] test fails in qemu: Network issue on SUT: can't resolve openqa.suse.de
- Description updated (diff)
- Category deleted (
Bugs in existing tests)
- Status changed from New to Workable
- Assignee set to dheidler
- Target version set to Milestone 28
- Estimated time set to 42.00 h
- Status changed from Workable to In Progress
This #60386 may be also related. Network problems in aarch64 with Online media.
- Category set to Spike/Research
- Category deleted (
Spike/Research)
- Has duplicate action #60386: [functional][u][aarch64] test fails in prepare_test_data - Network unreachable from within SUT added
- Status changed from In Progress to Blocked
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: toolchain_zypper
https://openqa.suse.de/tests/3715248
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
- Target version changed from Milestone 28 to Milestone 30
moving to current Milestone
- Category set to Bugs in existing tests
- Status changed from Blocked to Resolved
- This doesn't seem to happen anymore since 104.1
- This is/was a produce bug so I replaced the reference to this ticket in the latest failing build with the reference to the bug
so that the bug reference will be carried over when there should be a regression.
dheidler wrote:
- This doesn't seem to happen anymore since 104.1
- This is/was a produce bug so I replaced the reference to this ticket in the latest failing build with the reference to the bug
so that the bug reference will be carried over when there should be a regression.
https://bugzilla.suse.com/show_bug.cgi?id=1158025
Also available in: Atom
PDF