action #117424
closed[qe-core][sle15sp5][functional]test fails in network_hostname
0%
Description
Observation¶
openQA test in scenario sle-15-SP5-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 15.2
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by rfan1 over 1 year ago
- Target version deleted (
QE-Core: Ready)
I did some investigation on this failure, and found some progress tickets and one bug:
https://progress.opensuse.org/issues/102224
https://progress.opensuse.org/issues/107323
https://bugzilla.suse.com/show_bug.cgi?id=1162987
===================================
My concern is that, seems no test code to assign the host name to "linux*"
# Test died: command 'hostname | grep -E "linux-[[:alnum:]]{4}"' failed at /usr/lib/os-autoinst/testapi.pm line 922.
We only set the temporary host name to "myguest" with the setting below:
NICTYPE_USER_OPTIONS hostname=myguest
So, IMO, after the system reboot, the host name should be set back to "install".
Updated by openqa_review over 1 year 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/9759062#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 28 days if nothing changes in this ticket.
Updated by rfan1 over 1 year ago
https://github.com/yast/yast-network/blob/master/doc/hostname.md#installation-proposals
YaST tries to configure the local system hostname during installation. Currently (since SLE 15 SP2) YaST configures target system hostname only if it is explicitly set when booting installation with linuxrc's hostname option. In all other cases no hostname is proposed and you have to set the hostname later when booted into installed system.
Updated by rfan1 over 1 year ago
- Assignee deleted (
rfan1)
If hostname boot option is not used:
linuxrc doesn't write /etc/install.inf::Hostname, so it is not present.
linuxrc writes /etc/install.inf::SetHostnameUsed=0.
linuxrc sets the transient hostname to install.
Updated by rfan1 over 1 year ago
Updated by amanzini over 1 year ago
- Related to action #120246: [security][15sp4][QU1] test fails in hostname_inst on ppc64le added