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.

One of our customers is running Satellite 6 in HA configuration. His nodes hostnames are not same. When updating nodes, he needs to change the hostname of second and other nodes, otherwise the installation fails.

The request is to make Satellite use FQDN instead of hostname, during the installation.

This is covered by BZ1160344.  A workaround is available by following the HA Satellite environment document produced by the RefArch team.  There's a script to add multiple hostnames to the Satellite certificates and includes other considerations about how to have a highly available environment.

https://access.redhat.com/articles/2474581

*** This bug has been marked as a duplicate of bug 1160344 ***