Bug 692340 - Certificate Pending Forever?
Summary: Certificate Pending Forever?
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Toman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-31 04:53 UTC by David Le Sage
Modified: 2015-03-23 00:41 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-20 12:17:46 UTC
Type: ---


Attachments (Terms of Use)

Description David Le Sage 2011-03-31 04:53:12 UTC
Description of problem:
Note sure if this is a bug... I just tried to log an issue using the new version of abrt. I opted to send the debug trace to the server for processing and now I am receiving this message over and over in the "Analyzing" window without it ever resolving:

Certificate is signed by an untrusted issuer: 'E=mtoman,CN=retrace01.fedoraproject.org,OU=BaseOS,O=Red Hat,L=Brno,C=CZ'.
PENDING
Certificate is signed by an untrusted issuer: 'E=mtoman,CN=retrace01.fedoraproject.org,OU=BaseOS,O=Red Hat,L=Brno,C=CZ'.
PENDING
Certificate is signed by an untrusted issuer: 'E=mtoman,CN=retrace01.fedoraproject.org,OU=BaseOS,O=Red Hat,L=Brno,C=CZ'.
PENDING
Certificate is signed by an untrusted issuer: 'E=mtoman,CN=retrace01.fedoraproject.org,OU=BaseOS,O=Red Hat,L=Brno,C=CZ'.
PENDING
Certificate is signed by an untrusted issuer: 'E=mtoman,CN=retrace01.fedoraproject.org,OU=BaseOS,O=Red Hat,L=Brno,C=CZ'.
PENDING
Certificate is signed by an untrusted issuer: 'E=mtoman,CN=retrace01.fedoraproject.org,OU=BaseOS,O=Red Hat,L=Brno,C=CZ'.
PENDING
Certificate is signed by an untrusted issuer: 'E=mtoman,CN=retrace01.fedoraproject.org,OU=BaseOS,O=Red Hat,L=Brno,C=CZ'.
PENDING
Certificate is signed by an untrusted issuer: 'E=mtoman,CN=retrace01.fedoraproject.org,OU=BaseOS,O=Red Hat,L=Brno,C=CZ'.
PENDING

Version-Release number of selected component (if applicable):
abrt-2.0.0-2.fc15.x86_64

Comment 1 David Le Sage 2011-03-31 04:57:51 UTC
I may have spoken too soon as it eventually did resolve.  I am not sure if it was meant to take this long.  After I did that, though, I encountered this message:


Need writable directory, but '/var/spool/abrt/ccpp-1300937127-8476' is not writable. Move it to '/home/dlesage/.abrt/spool' and operate on the moved copy?


and when I tried to submit the bug, it claimed I had not submitted my password:

Empty login or password, please check /etc/abrt/plugins/Bugzilla.conf

 though I had done so by configuring the Bugzilla plug in's settings.  :-(

Comment 2 David Le Sage 2011-03-31 05:04:54 UTC
I manually edited /etc/abrt/plugins/Bugzilla.conf but abrt still claims the login or password are empty.  After running abrt, I opened Bugzilla.conf again and the username and password were still there.


Apologies if these should be broken down into separate bug reports - they seem like unrelated issues now.

Comment 3 Jiri Moskovcak 2011-03-31 08:01:44 UTC
(In reply to comment #1)
> I may have spoken too soon as it eventually did resolve.  I am not sure if it
> was meant to take this long.  After I did that, though, I encountered this
> message:
> 

- yes, it's normal to take few (or more..) minutes depending on the size of crashed application and it's dependencies

> 
> Need writable directory, but '/var/spool/abrt/ccpp-1300937127-8476' is not
> writable. Move it to '/home/dlesage/.abrt/spool' and operate on the moved copy?
> 

- this is correct behavior

> 
> and when I tried to submit the bug, it claimed I had not submitted my password:
> 
> Empty login or password, please check /etc/abrt/plugins/Bugzilla.conf
> 
>  though I had done so by configuring the Bugzilla plug in's settings.  :-(

- and this sounds like a bug

Comment 4 Michal Toman 2011-05-06 09:41:47 UTC
Certificate issue fixed in upstream git.


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