Bug 1126164 - python-bugzilla: nosslverify suggested even when using nosslverify
Summary: python-bugzilla: nosslverify suggested even when using nosslverify
Alias: None
Product: Fedora
Classification: Fedora
Component: python-bugzilla
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-08-02 22:44 UTC by Need Real Name
Modified: 2014-08-05 09:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-08-05 09:54:06 UTC

Attachments (Terms of Use)

Description Need Real Name 2014-08-02 22:44:17 UTC
Description of problem:

the --nosslverify option is suggested even when it's used:

% bugzilla --nosslverify attach --get=145244                                                                                                                                                                                        
hostname 'bugs.FreeBSD.org' doesn't match either of 'www.freebsd.org', 'freebsd.org'

If you trust the remote server, you can work around this error with:
  bugzilla --nosslverify ...

Version-Release number of selected component (if applicable):
1.1.0 with default bz patched:

-default_bz = 'https://bugzilla.redhat.com/xmlrpc.cgi'
+default_bz = 'https://bugs.FreeBSD.org/bugzilla/xmlrpc.cgi'

How reproducible:

See above

Steps to Reproduce:

See above

Actual results:

see above

Expected results:

Attachment downloaded

Additional info:

Comment 1 Cole Robinson 2014-08-05 09:54:06 UTC
Thanks for the report, fixed upstream now:

commit 531c99ec8187c4b919b2a290b25a3f0f086cab47
Author: Cole Robinson <crobinso@redhat.com>
Date:   Tue Aug 5 11:04:03 2014 +0200

    bugzilla: Propagate nosslverify when fetching attachments (bz 1126164)

commit e50ff140cad6060689546bc22a65eb97c8e889f2
Author: Cole Robinson <crobinso@redhat.com>
Date:   Tue Aug 5 10:57:31 2014 +0200

    bin/bugzilla: Log debug info for SSL errors

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