Bug 1224462

Summary: RC2 Tik installer / first boot doesn't prompt for hostname
Product: [openSUSE] openSUSE Aeon Reporter: Mike Watkins <solutionroute>
Component: InstallationAssignee: Richard Brown <rbrown>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Minor    
Priority: P5 - None CC: solutionroute
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Mike Watkins 2024-05-20 02:30:48 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36
Build Identifier: 

Aeon is a turnkey solution and a hostname - blank if expected to be set via a corp or home DHCP, manually set if not - should be part of the install (preferable) or first boot.

Reproducible: Always

Steps to Reproduce:
1.Install
Actual Results:  
No hostname is gathered during the install or first boot and therefore not set.

Expected Results:  
Provide opportunity for user to enter a hostname and set /etc/hostname, optionally leaving blank for DHCP situations.

It's a small thing that most with-it users will know how to address, but would make the system more finished at first boot.
Comment 1 Richard Brown 2024-05-21 08:02:02 UTC 
Maybe it's a controversial take but...what does the hostname matter for most Desktop users?

They never see it, they never need it

And those who do can just run hostnamectl, no?
Comment 2 Mike Watkins 2024-05-22 04:59:22 UTC 
Feedback noted; I do accept that many don't need a hostname, although lazy developers might.

This desktop user lazy developer often tests code between machines; my network setup creates DNS entries based on machine hostnames, rather than the inverse.

Do agree that hostnamectl (and perhaps an entry in a tips faq at some point) solves it for all.
Comment 3 Richard Brown 2024-05-22 14:55:12 UTC 
You mean like we already have here? :)

https://en.opensuse.org/Portal:Aeon#Set_hostname
Comment 4 Mike Watkins 2024-05-22 15:01:48 UTC 
Yes, exactly like that. ;-) Case closed?
Comment 5 Richard Brown 2024-05-22 15:27:03 UTC 
Yeah, for now at least :)
Comment 6 Richard Brown 2024-05-24 12:39:37 UTC 
of course there's another solution also

Ignition/Combustion

As the Aeon install media fully supports either, all it would take is someone putting an ignition config in an ignition direction on the ignition partition of the Aeon Installer USB stick, and they'd also be able to set the hostname

reproducibly even

on every install that uses that stick

and they dont even need to learn ignition or combustion config syntax because https://opensuse.github.io/fuel-ignition/ can generate that for stuff like setting the hostname
Comment 7 Mike Watkins 2024-05-24 22:39:00 UTC 
For hostname, hostnamectl is the easiest solution. I have taken to using combustion for other things in recent tests, although I have been facing some errors which leave me at an emergency prompt.

That leads me to ask: Is it possible under Tik that combustion runs before the network is defined?
Comment 8 Richard Brown 2024-05-24 22:40:23 UTC 
(In reply to Mike Watkins from comment #7)
> For hostname, hostnamectl is the easiest solution. I have taken to using
> combustion for other things in recent tests, although I have been facing
> some errors which leave me at an emergency prompt.
> 
> That leads me to ask: Is it possible under Tik that combustion runs before
> the network is defined?

That’s the default behaviour unless the user explicitly requests the network in combustion.. and even then combustion can be used to redefine it