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 .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 2259206 - Provisioning rhel9 with a dedicated provisioning interface results in an extra host created on Satellite
Summary: Provisioning rhel9 with a dedicated provisioning interface results in an extr...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.14.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-01-19 14:17 UTC by Joniel Pasqualetto
Modified: 2024-06-06 17:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:00:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 37098 0 Normal Ready For Testing Provisioning rhel9 with a dedicated provisioning interface results in an extra host created 2024-02-19 13:05:47 UTC
Red Hat Issue Tracker   SAT-22579 0 None Migrated None 2024-06-06 16:59:59 UTC
Red Hat Knowledge Base (Solution) 7052982 0 None None None 2024-01-23 15:00:14 UTC

Description Joniel Pasqualetto 2024-01-19 14:17:35 UTC
Description of problem:

Provisioning a RHEL9 system with a dedicated nic for provisioning and another as primary results in a duplicated host created on satellite, with the name defined on the provisioning interface.

This happens because we're using the rhsm component of anaconda to register the system. At that point of the installation, the host is using the hostname that it got from the dhcp. Then it registers into Satellite with that name.

Later, anaconda will update the name for the name of the primary interface, but at that point the extra host already exists on Satellite.

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

Satellite 6.14

How reproducible:


Steps to Reproduce:
1. Create a host with 2 nics. Define one as primary and other as provisioning
2. Provision the host with RHEL9 and default templates
3. Observe that you'll have 2 hosts created: one with the primary hostname and one with the provisioning hostname

Actual results:
Two hosts created on Satellite

Expected results:
Single host created on Satellite

Additional info:
A workaround is to add a %pre script that set the primary hostname into anaconda at an early stage, before rhsm step is executed:

~~~
%pre
hostnamectl set-hostname --static <%= @host.name %>
%end
~~~

Comment 5 Eric Helms 2024-06-06 17:00:01 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 "SAT-" 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.