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.

Description of problem:

Currently Signo requires the user to access Satellite 6 via FQDN only, and only the FQDN that the certs were generated with at install time.  


In a production deployment this is not that big of a deal, but for developers, especially ones that are using vms to spin up preinstalled katello/satellite instances this is a huge pain.

For example, I typically have vm's that all use the same fake hostname (katello.devel).  I can spin them up with a version of katello already installed. So i may have 5 or 10 vms all with the same hostname of katello.devel. Now with signo i have to modify my /etc/hosts file between access to every one.  Previously i could just go back and forth between the ip addresses of the different katello instances.

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Related PRs:
https://github.com/Katello/signo/pull/15
https://github.com/Katello/katello/pull/2544
https://github.com/theforeman/foreman/pull/742

It should work as long as your virtuals can resolve their hostnames locally. Also note that if you have problems with certificate you can set verify_certificate to false in signo configuration.

Moving this to be tested during MDP3, not critical for MDP2 success story

removing signo component and moving these bugs to 'Infrastructure'

*** Bug 996684 has been marked as a duplicate of this bug. ***

Moving to 6.0.4 for QE purposes.