Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1210336[details]
contenthostduplicate screenshot
Description of problem:
Customer is provisioning new hosts in vmware vsphere from satellite 6.2.2 (fresh installation) . They found duplicate host entry, one with shortname, one with fqdn.
The issue is similar of Bug 1356714. As per recommendation, errata is applied
and packages are up-to-date but the issue is revisited and hosts are having duplicate entry in satellite GUI.
Version-Release number of selected component (if applicable):
satellite-6.2.2
How reproducible:
--As per cu--
OK, so I have my vSphere (5.5) clusters added as compute resources. I build a machine using compute profiles I setup. The server builds the VM fine but once the packages have installed and goes through the postbuild is when a second entry is created, specifically around the time it tries to register the system. When it registers the system it creates a new system in hosts without an FQDN, as a result it even fails to install VMware tools despite it's part of the content view.
Actual results:
Duplicate hosts entry in sat 6.2.2
Expected results: