+++ This bug was initially created as a clone of Bug #681132 +++

Description of problem:
Add/Remove software (using pirut) crashes on Startup when rhn-client-tools failed to verify the SSL certificate (eg. the given cert is not valid).

As James Antill adviced in #681132, now up2dateErrors.SSLCertificateVerifyFailedError inherits from RepoError, which should be correctly handled by pirut (should show some window with readable error message). But when this expection is raised, no fancy error message is shown. 

Version-Release number of selected component (if applicable):
RHEL Server 5.8
pirut-1.3.28-19.el5
rhn-client-tools-0.4.20-76.el5 (the latest version at the moment)

How reproducible:
always when SSL cert is not valid and that exception is raised

Steps to Reproduce:
1. register to Satellite
2. change SSLcert in /etc/sysconfig/rhn/up2date to some existing and (for another different Satellite) valid cert
3. run `yum check-update` - readable message is shown
4. run `pirut` - 'Exception Occured' window with traceback is shown + traceback in terminal (when run from terminal)

From the Satellite devel/qa point of view this issue is fixed in rhn-client-tools, but the other part of problem remains in pirut.


--- Additional comment from james.antill on 2011-03-01 09:08:39 EST ---

  File "/usr/share/rhn/up2date_client/up2dateAuth.py", line 186, in login
    li = server.up2date.login(systemId)
  File "/usr/share/rhn/up2date_client/rhnserver.py", line 64, in __call__
    raise up2dateErrors.SSLCertificateVerifyFailedError()
SSLCertificateVerifyFailedError: The SSL certificate failed verification.

--- Additional comment from msuchy on 2011-03-01 10:26:23 EST ---

Well, the cause of this is that you have bad SSL certificate to access to rhn.redhat.com or you RHN Satellite. There is nothing we can do that about that. Reporter should use correct certificate.
I will ignore this part.

What we can fix is that Traceback. And it should be part of GUI/CLI tool using this plugin to catch this exception and provid nice error message - or in case of pirut - to provide nice error window. Presumable with some Cancel/Try Again.

James, do you agree, that pirut should catch this exception? If yes, can you take this BZ back. Otherwise I'm going to close it as there is nothing I can fix in plugin.

--- Additional comment from james.antill on 2011-03-01 12:21:16 EST ---

Changing the GUI significantly at this point is ... unlikely.

In general we don't want to be catching 666 random exceptions within the core, so we'd "expect" that the rhn plugin would catch the exception and rethrow as RepoError/NoMoreMirrorsRepoError/RepoMDError or even PluginYumExit (I'm not sure what pirut does with the later though).


--- Additional comment from mmraka on 2011-10-06 07:25:50 EDT ---

Backported change from spacewalk master as
------------------------------------------------------------------------
r207195 | mmraka | 2011-10-06 13:24:17 +0200 (Thu, 06 Oct 2011) | 5 lines

681132 - inherit SSLCertificateVerifyFailedError from RepoError

backported from 3ef12a289c1f1341144caf2af1d2595cd1500a66
691188 - inherit SSLCertificateVerifyFailedError from RepoError

------------------------------------------------------------------------

--- Additional comment from errata-xmlrpc on 2011-12-20 10:37:42 EST ---

Bug report changed to ON_QA status by Errata System.
A QE request has been submitted for advisory RHBA-2011:12150-03
http://errata.devel.redhat.com/errata/show/12150

--- Additional comment from errata-xmlrpc on 2011-12-20 10:37:44 EST ---

Bug report changed to ON_QA status by Errata System.
A QE request has been submitted for advisory RHBA-2011:12150-03
http://errata.devel.redhat.com/errata/show/12150