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.
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. It was unfortunately not given priority Red Hat Enterprise Linux.
Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX.
To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you.
Description of problem: In /var/log/httpd/error_log there are multiple errors like the following: [Thu Oct 03 12:24:03.822256 2019] [wsgi:error] [pid 27323:tid 139771935762688] ERROR:root:code for hash blake2b was not found. [Thu Oct 03 12:24:03.822274 2019] [wsgi:error] [pid 27323:tid 139771935762688] Traceback (most recent call last): [Thu Oct 03 12:24:03.822277 2019] [wsgi:error] [pid 27323:tid 139771935762688] File "/usr/lib64/python3.6/hashlib.py", line 219, in <module> [Thu Oct 03 12:24:03.822279 2019] [wsgi:error] [pid 27323:tid 139771935762688] globals()[__func_name] = __get_hash(__func_name) [Thu Oct 03 12:24:03.822281 2019] [wsgi:error] [pid 27323:tid 139771935762688] File "/usr/lib64/python3.6/hashlib.py", line 130, in __get_openssl_constructor [Thu Oct 03 12:24:03.822283 2019] [wsgi:error] [pid 27323:tid 139771935762688] return __get_builtin_constructor(name) [Thu Oct 03 12:24:03.822284 2019] [wsgi:error] [pid 27323:tid 139771935762688] File "/usr/lib64/python3.6/hashlib.py", line 120, in __get_builtin_constructor [Thu Oct 03 12:24:03.822286 2019] [wsgi:error] [pid 27323:tid 139771935762688] raise ValueError('unsupported hash type ' + name) [Thu Oct 03 12:24:03.822289 2019] [wsgi:error] [pid 27323:tid 139771935762688] ValueError: unsupported hash type blake2b The pids in error messages refer to "(wsgi:ipa)" and "(wsgi:kdcproxy)" processes Version-Release number of selected component (if applicable): # rpm -q ipa-server ipa-server-4.8.0-11.module+el8.1.0+4247+9f3fd721.x86_64 python version: python36-3.6.8-2.module+el8.1.0+3334+5cb623d7.x86_64 How reproducible: Steps to Reproduce: 1. install ipa-server 2. look in /var/log/httpd/error_log Actual results: error messages Expected results: no error messages