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.
Description of problem:
This is more of an RFE i would assume but I am filing it as a Bug for now.
On Capsule 6.10, if satellite-installer fails with some error related to SSL, It's prints a message saying
"Check /var/log/foreman/production.log on Foreman server for detailed information"
The term Foreman server is for upstream. We should either replace it i.e.
"Check /var/log/foreman/production.log on the Satellite server for detailed information"
or, we should mention the FQDN of satellite:
"Check /var/log/foreman/production.log on the satellite.example.com server for detailed information"
Version-Release number of selected component (if applicable):
Red Hat Capsule 6.10 [ satellite-installer ]
How reproducible:
Mostly when the installer fails due to an SSL issue
Steps to Reproduce:
1. Install satellite and capsule 6.10 with custom certs
2. Run "satellite-installer --certs-reset" on satellite to revert back to Self-Signed cert.
3. Don't create a new certificate tar for the capsule but use the existing one which still has the old certificate rpm and then execute satellite-installer command on the capsule and monitor the output.
Actual results:
2021-08-17 21:34:06 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[capsule.example.com]: Failed to call refresh: Error making PUT request to https://satellite.example.com/api/v2/smart_proxies/2/refresh: Response: 500 Internal Server Error: Check /var/log/foreman/production.log on Foreman server for detailed information
2021-08-17 21:34:06 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[capsule.example.com]: Error making PUT request to https://satellite.example.com/api/v2/smart_proxies/2/refresh: Response: 500 Internal Server Error: Check /var/log/foreman/production.log on Foreman server for detailed information
2021-08-17 21:34:07 [NOTICE] [configure] System configuration has finished.
Expected results:
Same as what is mentioned in the Description part i.e. improvement of error message statement.
Additional info:
NA
Referring to Foreman/Satellite server is difficult to accomplish without introducing upstream/downstream differences that are harder to maintain.
So I went the route of using the FQDN instead. This is even more specific and should inform the user exactly where to look
The PR is at https://github.com/theforeman/puppet-foreman/pull/988
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 (Moderate: Satellite 6.10 Release), 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/RHSA-2021:4702