Bug 1169033 - [abrt] plague-client: SSLConnection.py:112:sendall:Error: [('asn1 encoding routines', 'ASN1_item_verify', 'unknown message digest algorithm'), ('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')]
Summary: [abrt] plague-client: SSLConnection.py:112:sendall:Error: [('asn1 encoding ro...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plague
Version: 21
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:a39f881a737e408b11300536513...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-29 06:39 UTC by Julian Sikorski
Modified: 2015-12-02 16:36 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 05:19:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (2.28 KB, text/plain)
2014-11-29 06:39 UTC, Julian Sikorski
no flags Details
File: dso_list (68 bytes, text/plain)
2014-11-29 06:39 UTC, Julian Sikorski
no flags Details
File: environ (3.26 KB, text/plain)
2014-11-29 06:39 UTC, Julian Sikorski
no flags Details

Description Julian Sikorski 2014-11-29 06:39:24 UTC
Description of problem:
I tried to build an RPM fusion package by calling make build.

Version-Release number of selected component:
plague-client-0.4.5.8-19.fc21

Additional info:
reporter:       libreport-2.3.0
cmdline:        /usr/bin/python /usr/bin/plague-client build qmc2 qmc2-0_46-1_fc21 rawhide-nonfree
executable:     /usr/bin/plague-client
kernel:         3.17.4-300.fc21.x86_64
runlevel:       N 5
type:           Python
uid:            500

Truncated backtrace:
SSLConnection.py:112:sendall:Error: [('asn1 encoding routines', 'ASN1_item_verify', 'unknown message digest algorithm'), ('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')]

Traceback (most recent call last):
  File "/usr/bin/plague-client", line 422, in <module>
    cli = PlagueClient(os.path.expanduser(cfg_file))
  File "/usr/bin/plague-client", line 85, in __init__
    self._check_api_version(self._server)
  File "/usr/bin/plague-client", line 90, in _check_api_version
    server_ver = server.api_version()
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1578, in __request
    verbose=self.__verbose
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request
    return self.single_request(host, handler, request_body, verbose)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1292, in single_request
    self.send_content(h, request_body)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1439, in send_content
    connection.endheaders(request_body)
  File "/usr/lib64/python2.7/httplib.py", line 991, in endheaders
    self._send_output(message_body)
  File "/usr/lib64/python2.7/httplib.py", line 844, in _send_output
    self.send(msg)
  File "/usr/lib64/python2.7/httplib.py", line 820, in send
    self.sock.sendall(data)
  File "/usr/lib/python2.7/site-packages/plague/SSLConnection.py", line 112, in sendall
    sent = con.send(data, flags)
Error: [('asn1 encoding routines', 'ASN1_item_verify', 'unknown message digest algorithm'), ('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')]

Local variables in innermost frame:
curtime: 1417242650.836792
read: []
self: <OpenSSL.SSL.Connection object at 0x7fa9c66f0328>
timeout: 20
write: [<OpenSSL.SSL.Connection object at 0x7fa9c66f0328>]
flags: 0
starttime: 1417242650.636169
excpt: []
con: <OpenSSL.SSL.Connection object at 0x7fa9c66f0328>
data: "POST /RPC2 HTTP/1.1\r\nHost: buildsys.rpmfusion.org:8887\r\nAccept-Encoding: gzip\r\nUser-Agent: pyOpenSSL_XMLRPC/0.12 - xmlrpclib.py/1.0.1 (by www.pythonware.com)\r\nContent-Type: text/xml\r\nContent-Length: 105\r\n\r\n<?xml version='1.0'?>\n<methodCall>\n<methodName>api_version</methodName>\n<params>\n</params>\n</methodCall>\n"
sent: -1
origlen: 311

Comment 1 Julian Sikorski 2014-11-29 06:39:27 UTC
Created attachment 962651 [details]
File: backtrace

Comment 2 Julian Sikorski 2014-11-29 06:39:28 UTC
Created attachment 962652 [details]
File: dso_list

Comment 3 Julian Sikorski 2014-11-29 06:39:29 UTC
Created attachment 962653 [details]
File: environ

Comment 4 Mamoru TASAKA 2014-11-29 09:10:23 UTC
Ref: bug 1071615

Comment 5 Fedora End Of Life 2015-11-04 14:42:00 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-12-02 05:19:24 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.