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.
Using latest nightly and encountered the following error: No smart proxy server found on [] and is not in trusted_puppetmaster_hosts
As you can see it wasn't listing the connecting smart proxy / host. Dug into the code and found the following section of code:
@
if certificate.subject_alternative_names
request_hosts += certificate.subject_alternative_names
elsif certificate.subject
request_hosts << certificate.subject
end
@
Testing of certificate.subject_alternative_names always evaluates to true even when no SAN. This results in request_hosts to be empty and authentication of the request fails.
Build: Satellite 6.2 Snap 19.1
Puppet was installed and configured on provisioned hosts and puppet reports were successfully submitted.
Also, Puppet master is running successfully..
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1501
Using latest nightly and encountered the following error: No smart proxy server found on [] and is not in trusted_puppetmaster_hosts As you can see it wasn't listing the connecting smart proxy / host. Dug into the code and found the following section of code: @ if certificate.subject_alternative_names request_hosts += certificate.subject_alternative_names elsif certificate.subject request_hosts << certificate.subject end @ Testing of certificate.subject_alternative_names always evaluates to true even when no SAN. This results in request_hosts to be empty and authentication of the request fails.