action #102224
closed[qe-core] test fails in network_hostname - incorrect hostname + test runs in full blown installation
0%
Description
Observation¶
openQA test in scenario sle-15-SP4-Online-x86_64-network_configuration@64bit fails in
network_hostname
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainer: jrivera@suse.com Verify that DHCLIENT_SET_HOSTNAME preloaded from control file does not overwrite the customer selection and check the hostname in the installed system
Reproducible¶
Fails since (at least) Build 43.1
Further details¶
Always latest result in this scenario: latest
notes¶
As a plus, this test can be moved to an extratest at the end, with the corresponding soft failure.
Also see: https://bugzilla.suse.com/show_bug.cgi?id=1162987
Acceptance Criteria¶
AC1: Move network_hostname to when booting from already installed HDD.
Updated by szarate over 2 years ago
- Related to coordination #95935: [epic][qe-core] Limit installation tests by depending more on the create_hdd_* jobs. added
Updated by szarate over 2 years ago
- Subject changed from [qe-core] test fails in network_hostname - incorrect hostname to [qe-core] test fails in network_hostname - incorrect hostname + test runs in full blown installation
Updated by openqa_review over 2 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/7716745
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by tjyrinki_suse over 2 years ago
- Status changed from New to Workable
- Start date deleted (
2021-11-10)
Updated by tjyrinki_suse over 2 years ago
- Status changed from Workable to New
Probably needs refining together.
Updated by openqa_review over 2 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/7805904
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review over 2 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/7887830
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review over 2 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/7924210
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review over 2 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/7977286
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review about 2 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/8089615
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by tjyrinki_suse about 2 years ago
- Category changed from Bugs in existing tests to Spike/Research
- Status changed from New to Workable
Updated by tjyrinki_suse about 2 years ago
Needs investigation whether we are able to debug this problem.
Updated by tjyrinki_suse about 2 years ago
- Description updated (diff)
- Target version deleted (
QE-Core: Ready)
Updated by tjyrinki_suse about 2 years ago
Needs refinement in the description to be workable.
Updated by apappas about 2 years ago
- Status changed from New to Workable
Refinement:
- Why should we run this test?
Updated by openqa_review about 2 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/8292431
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by tjyrinki_suse about 2 years ago
Discussed with Joaquin, there are changes needed for newer product and notes will be also at:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14565
Updated by openqa_review about 2 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/8558425#step/network_hostname/1
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 52 days if nothing changes in this ticket.
Updated by openqa_review almost 2 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/8752538#step/network_hostname/1
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 104 days if nothing changes in this ticket.
Updated by zluo about 1 year ago
- Status changed from Workable to Resolved
- Assignee set to zluo
https://openqa.suse.de/tests/10524819 no issue anymore.