Bug 1382311
Summary: | ISE: rhnpush with connection by https on Fedoras | ||
---|---|---|---|
Product: | [Community] Spacewalk | Reporter: | Pavel Studeník <pstudeni> |
Component: | Server | Assignee: | Tomáš Kašpárek <tkasparek> |
Status: | CLOSED EOL | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.5 | CC: | eherget, jdobes, jhutar, mmraka, tlestach |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-06 13:49:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1310034 |
Description
Pavel Studeník
2016-10-06 10:32:16 UTC
Cannot reproduce this bug. I'm using Spacewalk on Fedora 24 and SSL is on. rhnpush via https as well. I can't reproduce this bug. I'm using fresh-installed Spacewalk on Fedora 24. Steps I did: dnf -y install mod_ssl openssl systemctl restart httpd # as described here: https://docs.fedoraproject.org/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mod_ssl-enabling.html rhnpush -c fedora24-x86_64 -u *** -p *** --server=https://ibm-x3650m4-03-vm05.lab.eng.brq.redhat.com/APP redhat-rpm-config-42-2.fc24.noarch.rpm rpm -q python3-cryptography python2-cryptography rhnpush mod_ssl python3-cryptography-1.5.3-3.fc24.x86_64 python2-cryptography-1.5.3-3.fc24.x86_64 rhnpush-5.5.105-1.fc24.noarch mod_ssl-2.4.25-1.fc24.x86_64 Closing this bug because we were not able to reproduce in later version of Spacewalk. Believe this has been fixed. I still can see following errors in logs on Fedora 24/25 python2-cryptography-1.5.3-3.fc24.x86_64 python2-cryptography-1.5.3-3.fc25.x86_64 >> tail /var/log/httpd/error_log [Sun ...] [wsgi:error] [pid 12170] [client ] Binding.init_static_locks() [Sun ...] [wsgi:error] [pid 12170] [client ] File "/usr/lib64/python2.7/site-packages/cryptography/hazmat/bindings/openssl/binding.py", line 180, in init_static_locks [Sun ...] [wsgi:error] [pid 12170] [client ] cls._ensure_ffi_initialized() [Sun ...] [wsgi:error] [pid 12170] [client ] File "/usr/lib64/python2.7/site-packages/cryptography/hazmat/bindings/openssl/binding.py", line 175, in _ensure_ffi_initialized [Sun ...] [wsgi:error] [pid 12170] [client ] cls._register_osrandom_engine() [Sun ...] [wsgi:error] [pid 12170] [client ] File "/usr/lib64/python2.7/site-packages/cryptography/hazmat/bindings/openssl/binding.py", line 140, in _register_osrandom_engine [Sun ...] [wsgi:error] [pid 12170] [client ] _openssl_assert(cls.lib, cls.lib.ERR_peek_error() == 0) [Sun ...] [wsgi:error] [pid 12170] [client ] File "/usr/lib64/python2.7/site-packages/cryptography/hazmat/bindings/openssl/binding.py", line 62, in _openssl_assert [Sun ...] [wsgi:error] [pid 12170] [client ] errors_with_text [Sun ...] [wsgi:error] [pid 12170] [client ] InternalError: Unknown OpenSSL error. This error is commonly encountered when another library is not cleaning up the OpenSSL error stack. If you are using cryptography with another library that uses OpenSSL try disabling it before reporting a bug. Otherwise please file an issue at https://github.com/pyca/cryptography/issues with information on how to reproduce this. ([_OpenSSLErrorWithText(code=151441516L, lib=9, func=109, reason=108, reason_text='error:0906D06C:PEM routines:PEM_read_bio:no start line'), _OpenSSLErrorWithText(code=151441516L, lib=9, func=109, reason=108, reason_text='error:0906D06C:PEM routines:PEM_read_bio:no start line')]) [Sun Jul 23 17:04:06.307375 2017] [mpm_prefork:notice] [pid 21598] AH00170: caught SIGWINCH, shutting down gracefully Pavel, two guys said they cannot reproduce the bug. I'd expect to see more detailed reproducer steps if reopened. *** Bug 1346293 has been marked as a duplicate of this bug. *** Sometimes I received this traceback during uploading package Package ... Using POST request Waiting 3 seconds and trying again... Giving up after 3 attempts Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f01f04ae510> Traceback (most recent call last): File "/usr/lib64/python3.5/weakref.py", line 117, in remove TypeError: 'NoneType' object is not callable Spacewalk 2.8 (and older) has already reached it's End Of Life. Thank you for reporting this issue and we are sorry that we were not able to fix it before end of life. If you would still like to see this bug fixed and are able to reproduce it against current version of Spacewalk 2.9, you are encouraged change the 'version' and re-open it. |