Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Freshly installed Leap 16 has hostname and prompt set to agama #1414

Closed
lkocman opened this issue Jun 28, 2024 · 4 comments
Closed

Freshly installed Leap 16 has hostname and prompt set to agama #1414

lkocman opened this issue Jun 28, 2024 · 4 comments
Assignees
@teclator
Labels
agama-live

Comments

@lkocman
Copy link
Contributor

lkocman commented Jun 28, 2024

Hello team

it seems that hostname is copied from agama live dvd. I'd expect default hostname to be set to localhost.localdomain or something.
hostname-logs.zip

image
@imobachgs
Copy link
Contributor

OK, we need to check that behavior. @teclator please, could you have a look?

About Leap 16.0, it looks like you could install it 😄 However, we were having some troubles two days ago. Do we need to do anything to get the Leap 16.0 configuration working? Thanks!

@teclator
Copy link
Contributor

teclator commented Jul 2, 2024 •
edited
Loading

I would say that it is not copied to the target system but set by NetworkManager when getting DHCP.

Agama has a one-shot service for setting the hostname when the installation boots, therefore the hostname will be used when requesting an address by DHCP (@lslezak should know more).

See net-dhcp-leases from a fresh installation

$ sudo virsh net-dhcp-leases default
 Expiry Time           MAC address         Protocol   IP address           Hostname   Client ID or DUID
------------------------------------------------------------------------------------------------------------
 2024-07-02 10:25:26   52:54:00:ae:4a:88   ipv4       192.168.100.161/24   agama      01:52:54:00:ae:4a:88

I guess that running hostnamectl at the installed system will show that it is the transient one, BTW we probably should just set the transient hostname when booting.

@teclator
Copy link
Contributor

teclator commented Jul 2, 2024

I need to check if using the transient one is fine with the current mDNS / Avahi documentation.

https://github.com/openSUSE/agama/blob/master/doc/avahi.md#using-mdns

@teclator teclator mentioned this issue Jul 3, 2024
Merged
teclator added a commit that referenced this issue Jul 3, 2024
@teclator
Set the transient hostname instead of the static (#1432)
fde719c 
## Problem

It has been reported that a fresh installation sets the hostname to
agama after booting the installed system which is ok for the installer
but looks weird for the installed system, therefore, we should try to
fix the issue avoiding to set agama as the hostname of the installed
system if not requested explicitly.

- #1414
-
https://trello.com/c/3XWqwiAb/3725-issue-agama-hostname-is-used-after-installation

## Solution

Set the transient hostname instead of the static one not sending it when
requesting a DHCP address.

**Note** In case that the hostname is set statically, it is not copied
to the target system.

## Test

Tested manually

![Screenshot from 2024-07-03
09-38-32](https://github.com/openSUSE/agama/assets/7056681/9dbc582a-27e2-403d-a2a7-a807d22f2430)
![Screenshot from 2024-07-03
09-43-25](https://github.com/openSUSE/agama/assets/7056681/f87fb58f-9f0c-489d-b6b4-e773d52d6661)
@teclator
Copy link
Contributor

teclator commented Jul 3, 2024

Fixed by #1432

@teclator teclator closed this as completed Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@teclator teclator

Labels
agama-live
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@imobachgs @lkocman @teclator