action #60293
closed
[functional][u] test fails in network_configuration
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-x86_64-network_configuration@64bit fails in
network_configuration
Tasks¶
- Apply a workaround to the new "default: no" until it is confirmed if this new default is expected behavior.
- Put the ticket back into new
- After confirmation, remove workaround and fix test.
Reproducible¶
Fails since (at least) Build 89.1
Expected result¶
Last good: sle-15-SP2-Online-x86_64-Build89.1-network_configuration@64bit
Further details¶
Always latest result in this scenario: latest
This looks as if some default was changed.
Needs further investigation.
- Subject changed from test fails in network_configuration to [functional][u] test fails in network_configuration
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: network_configuration
https://openqa.suse.de/tests/3699679
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: network_configuration
https://openqa.suse.de/tests/3715964
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: network_configuration
https://openqa.suse.de/tests/3766950
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
- Priority changed from Normal to High
This Testcase fails twice in osd. Could we get that fixed until beta2 in two weeks?
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Milestone 30
- Estimated time set to 42.00 h
- Status changed from Workable to In Progress
- Assignee set to zluo
network_configuration-inst-network-hostname-dns-tab created.
- Status changed from In Progress to Resolved
Also available in: Atom
PDF