action #60293
closed[functional][u] test fails in network_configuration
0%
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.
Updated by dheidler over 4 years ago
- Subject changed from test fails in network_configuration to [functional][u] test fails in network_configuration
Updated by okurz over 4 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: 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
Updated by okurz over 4 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: 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
Updated by okurz over 4 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: 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
Updated by maritawerner over 4 years ago
- Priority changed from Normal to High
This Testcase fails twice in osd. Could we get that fixed until beta2 in two weeks?
Updated by SLindoMansilla about 4 years ago
Waiting for confirmation that default value is set to no since SLE15-SP2: https://bugzilla.suse.com/show_bug.cgi?id=1158898#c7
Updated by SLindoMansilla about 4 years ago
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Milestone 30
- Estimated time set to 42.00 h
Updated by szarate about 4 years ago
My bad :/ I forgot about the workaround part: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9444
Updated by zluo about 4 years ago
- Status changed from Workable to In Progress
- Assignee set to zluo
take over and checking
Updated by zluo about 4 years ago
https://openqa.suse.de/tests/3822941#step/network_configuration/4 shows atm we have needle match issue, so fix this at first.
Updated by zluo about 4 years ago
network_configuration-inst-network-hostname-dns-tab created.
Updated by zluo about 4 years ago
http://f40.suse.de/tests/6781#step/network_configuration/5 looks good now
Updated by zluo about 4 years ago
- Status changed from In Progress to Resolved
https://openqa.suse.de/tests/3844655#step/network_configuration/5 fixed on osd now.
With https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9444 we have handled default:no correctly. So there is nothing more to do atm.