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:
Registration error do not show correct description like RHEL 7 for RHEL 8 when self signed certificates in Satellite and insecure option not selected.
Version-Release number of selected component (if applicable):
Satellite 6.13
How reproducible:
Always
Steps to Reproduce:
1. Install a Satellite 6.13 with self-signed certicates.
2. Register a client with the satellite without insecure option enabled.
3.
Actual results:
1) For RHEL 7 (proper error description):
# curl -sS 'https://<Satellite-hostname>/register?activation_keys=ak&force=true&ignore_subman_errors=true&lifecycle_environment_id=1&location_id=2&operatingsystem_id=1&organization_id=1&setup_insights=true&setup_remote_execution=true&setup_remote_execution_pull=true&update_packages=false' -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjo0LCJpYXQiOjE2NzU3NTE0MjMsImp0aSI6IjRkYmQ1ZGQxZTIyMDYxMzUxYWI3ODdjZmVkMDA3MWVhZjU5NjdiYTQyNzE0MmNmNzM5NmM0MTdjYmRkNmVkZjgiLCJleHAiOjE2NzU3NjU4MjMsInNjb3BlIjoicmVnaXN0cmF0aW9uI2dsb2JhbCByZWdpc3RyYXRpb24jaG9zdCJ9.lVE4-6ZBj-IT_PmXD9DhFO42ltQsDuPH5hM6IMupbpI' | bash
curl: (60) Peer's certificate issuer has been marked as not trusted by the user.
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
2) For RHEL 8 (do not show proper error description):
# curl -sS 'https://<Satellite-hostname>/register?activation_keys=ak&force=true&ignore_subman_errors=true&lifecycle_environment_id=1&location_id=2&operatingsystem_id=1&organization_id=1&setup_insights=true&setup_remote_execution=true&setup_remote_execution_pull=true&update_packages=false' -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjo0LCJpYXQiOjE2NzU3NTE0MjMsImp0aSI6IjRkYmQ1ZGQxZTIyMDYxMzUxYWI3ODdjZmVkMDA3MWVhZjU5NjdiYTQyNzE0MmNmNzM5NmM0MTdjYmRkNmVkZjgiLCJleHAiOjE2NzU3NjU4MjMsInNjb3BlIjoicmVnaXN0cmF0aW9uI2dsb2JhbCByZWdpc3RyYXRpb24jaG9zdCJ9.lVE4-6ZBj-IT_PmXD9DhFO42ltQsDuPH5hM6IMupbpI' | bash
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: https://curl.haxx.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Expected results:
Should show error message like RHEL 7:
~~~
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
~~~
Additional info:
No impact but simply an improvement request for better usability
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.