This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1918676 - Modifying the hostname is not being applied immediately
Summary: Modifying the hostname is not being applied immediately
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: initial-setup
Version: 8.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 8.0
Assignee: Martin Kolman
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-21 10:58 UTC by Renaud Métrich
Modified: 2024-03-25 17:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 15:02:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4710 0 None Migrated None 2023-09-18 15:02:36 UTC

Internal Links: 1918681

Description Renaud Métrich 2021-01-21 10:58:04 UTC 
Description of problem:

When modifying the hostname through using the initial-setup GUI or Text interface, upon exiting the tool, the hostname is not used on the system, as shown in the example below, consisting in renaming "vm-gui83" into "vm-gui83-renamed":

1. Before renaming

# hostnamectl | grep "vm-gui83"; cat /etc/hostname /proc/sys/kernel/hostname 
   Static hostname: vm-gui83
vm-gui83
vm-gui83

2. After renaming and clicking on "Apply" (GUI only)

# hostnamectl | grep "vm-gui83"; cat /etc/hostname /proc/sys/kernel/hostname 
   Static hostname: vm-gui83
Transient hostname: vm-gui83-renamed
vm-gui83
vm-gui83

3. After exiting the configuration tool

# hostnamectl | grep "vm-gui83"; cat /etc/hostname /proc/sys/kernel/hostname 
   Static hostname: vm-gui83
Transient hostname: vm-gui83-renamed
vm-gui83
vm-gui83

--> hostname not applied


In fact, in order for the hostname to apply really (reflecting in /proc/sys/kernel/hostname), it is necessary to wait for systemd-hostnamed service to exit, then issue a "hostnamectl" command. The systemd-hostnamed service will then discover that /etc/hostname (set by initial-setup) is different than current hostname (old not renamed "vm-gui83") and apply the modification.

The bug here is that initial-setup should modify the Static hostname upon finishing the configuration, not the Transient hostname.

4. After systemd-hostnamed exited and a "hostnamectl" was issue again

# hostnamectl | grep "vm-gui83"; cat /etc/hostname /proc/sys/kernel/hostname 
   Static hostname: vm-gui83-renamed
vm-gui83-renamed
vm-gui83-renamed

--> hostname finally applied


Version-Release number of selected component (if applicable):

initial-setup-0.3.81.6-1.el8.x86_64


How reproducible:

Always, see procedure above.
To start the initial-setup on boot, just enable "initial-setup-reconfiguration.service", "touch /.unconfigured" and reboot
Comment 2 RHEL Program Management 2023-09-18 15:00:44 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 3 RHEL Program Management 2023-09-18 15:02:40 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.