action #48416
open
[opensuse][leap] test fails in install_service - could not resolve host openqa.opensuse.org
Added by mlin7442 about 5 years ago.
Updated about 1 month ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Description
Observation¶
openQA test in scenario opensuse-15.1-DVD-x86_64-zdup-Leap-42.2-gnome@64bit-2G fails in
install_service
Test suite description¶
Looks like this is happened on 42.2/42.3 upgrade scenario(sporadic), I can't figure out.
Reproducible¶
Fails since (at least) Build 419.1 (current job)
Expected result¶
Last good: 417.2 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Priority changed from Normal to High
- Subject changed from test fails in install_service - could not resolve host openqa.opensuse.org to [functional][u] test fails in install_service - could not resolve host openqa.opensuse.org
- Target version set to Milestone 23
@mlin7442 isn't that a strong indication of a product regression if the network is down just one specific scenario?
- Status changed from New to Rejected
- Status changed from Rejected to New
- Description updated (diff)
but seems we don't have this issue on TW though...
- Subject changed from [functional][u] test fails in install_service - could not resolve host openqa.opensuse.org to [opensuse][leap] test fails in install_service - could not resolve host openqa.opensuse.org
- Assignee set to mlin7442
@mlin7442 please handle as product issue. Sorry, QSF-u does not have enough capacity to look into this issue.
- Target version changed from Milestone 23 to Milestone 24
- Target version changed from Milestone 24 to Milestone 25
- Target version changed from Milestone 25 to Milestone 26
- Target version changed from Milestone 26 to Milestone 30+
- Target version changed from Milestone 30+ to Milestone 30
bulk moved to M30 for revisiting
- Priority changed from High to Normal
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.
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.
Also available in: Atom
PDF