Project

General

Profile

Actions

action #177213

closed

coordination #169654: [epic] Create test scenarios for Agama

Add test cases for setting hostname in Agama via kernel params

Added by JERiveraMoya 2 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
2025-02-14
Due date:
% Done:

0%

Estimated time:

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:

Actions #1

Updated by lmanfredi 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to lmanfredi
Actions #2

Updated by lmanfredi 2 months ago

At the moment, without any setting, the default value for hostname it seems to be "localhost"

Actions #3

Updated by lmanfredi 2 months 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"

Actions #4

Updated by lmanfredi 2 months ago

Created PR#21248

Actions #5

Updated by lmanfredi 2 months 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

Actions #6

Updated by lmanfredi 2 months ago

Updated VRs for all ARCHs

Actions #7

Updated by lmanfredi 2 months ago

Removed VRs for ARCHs: ppc64le and s390x

Actions #8

Updated by JERiveraMoya about 2 months ago

  • Tags changed from qe-yam-feb-sprint-fy25 to qe-yam-mar-sprint-fy25
Actions #9

Updated by lmanfredi about 1 month ago

Updated VRs by using Build 60.3 Beta2

Actions #10

Updated by lmanfredi about 1 month ago

Updated VRs by using Build 61.3

Actions #11

Updated by lmanfredi about 1 month ago

Updated VRs with default and default unattended (test hostname by DHCP) and one test for extended (test hostname from test_data)

Actions #12

Updated by JERiveraMoya about 1 month ago

Merged, let's setup the test suite, schedule them in production/development job groups and resolve this ticket.

Actions #13

Updated by JERiveraMoya about 1 month ago

  • Subject changed from Add test cases for setting hostname in Agama to Add test cases for setting hostname in Agama via kernel params
Actions #14

Updated by lmanfredi about 1 month ago

Added test suites (sles_extended) in Job Templates for groups:

Actions #15

Updated by JERiveraMoya about 1 month ago

  • Status changed from In Progress to Resolved

lmanfredi wrote in #note-14:

Added test suites (sles_extended) in Job Templates for groups:

Please trigger the test suite as well, not just add them to configuration.

Actions #16

Updated by lmanfredi about 1 month ago · Edited

Triggered sles_extended for Job Group 607 passed

Triggered sles_extended for Job Group 612 passed

Actions

Also available in: Atom PDF