Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
IHAC, who wants to raise an RFE to improve error messages to make it easier to pinpoint the issue for anyone who will be in the same situation in the future. Here's the customer's observation and recommendation:
-----
So, I went digging thru source code to see what is IPA trying to do - at that stage it wanted to establish https connection towards Master using python-request module. It occurred to me, that system have http&https proxy configured in /etc/environment. When I unset this proxy, installation of replica was successful.
So, apparently, when request module failed to connect to master thru http/https, it threw "SSL verification failed" which is misleading. Proxy replied with another CA certificate so error should say something like "Certificate mismatch" - client already downloaded IPA CA certificate to trusted CA repository. Also, proxy reply came from other IP than IPA master, so maybe some check for http/s traffic hijack could be also a good to implement.
-----
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 7.7
ipa-server-4.6.5-11
How reproducible:
Always
Actual results:
# ipa-replica-install --password 'random_password' --server idm.example.com --domain example.com --setup-dns --setup-ca --no-forwarder
ipapython.admintool: DEBUG The ipa-replica-install command failed, exception: SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)
ipapython.admintool: ERROR [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)
ipapython.admintool: ERROR The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information
Expected results:
ipa-replica-install should perform a sanity check of the environment for proxy configuration, or scrub the environment so that proxy configuration does not cause installation to fail.
Additional info:
Frase Tweedal has the following suggestion in idm-tech mailing list:
Please file the RFE, but I think rather than change the error message, it should be to either sanity check the environment for proxy configuration, or scrub the environment so that proxy configuration does not cause installation to fail.
I don't think there's much we can do about the error message - certificate mismatch is what is causing the SSL/TLS verification failure. Most of the time a TLS library does not distinguish these cases.
Comment 8RHEL Program Management
2023-09-18 17:56:14 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 9RHEL Program Management
2023-09-18 18:01:13 UTC
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 "RHEL-" 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.