action #177213
opencoordination #169654: [epic] Create test scenarios for Agama
Add test cases for setting hostname in Agama
0%
Description
Motivation¶
Set hostname in different ways in Agama installer.
Check this conversation for more information:
https://suse.slack.com/archives/C082VE1U2F5/p1738930441550219
but summary is that at the moment are two ways:
(1) Agama by default takes the hostname from DHCP.
(2) Passing hostname= as a kernel command line parameter.
Acceptance criteria¶
- AC1: Add a validation post-installation for the (interactive and unattended) default installation to check hostname from dhcp.
- AC2: Add validation post-installation for (2) in existing test suite.
Additional information¶
As seems an overkill to create new test suites for (2) we should consider where we could include the 2nd way.
Similar test cases in YaST installer:
- https://openqa.suse.de/tests/16682150
- https://openqa.suse.de/tests/16682153 We should try to avoid checks during the installation process, and perform them after installation. When we add it to existing test suite we should try to include in the name if it is not too long.
Updated by lmanfredi 2 days ago
Passing hostname= as a kernel command line parameter works fine. E.g. in VRs by setting this param in var EXTRABOOTPARAMS
EXPECTED_INSTALL_HOSTNAME="suselinux"
EXTRABOOTPARAMS="live.password=nots3cr3t console=ttyS0 console=tty kernel.softlockup_panic=1 agama.install_url=http://openqa.suse.de/assets/repo/SLES-Packages-16.0-x86_64-Build5.1/ hostname=$EXPECTED_INSTALL_HOSTNAME"
Updated by lmanfredi about 22 hours ago ยท Edited
This new module tests/yam/validate/validate_hostname.pm should be included inside some yaml schedule file to avoid the CI GitHub error:
tests/yam/validate/validate_hostname.pm module is not used in any schedule
generated from CI static test detect_unused_modules
See comments in Slack channel