Bug 1402906

Summary:	Incorrectly raised exception in rhn-custom-info
Product:	Red Hat Satellite 5	Reporter:	Lukáš Hellebrandt <lhellebr>
Component:	Other	Assignee:	Jan Dobes <jdobes>
Status:	CLOSED DEFERRED	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	tlestach
Target Milestone:	---
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:	2018-04-09 15:25:36 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:

Description Lukáš Hellebrandt 2016-12-08 15:26:43 UTC

Description of problem:
BZ created based on info in bug 1386615. When using rhn-custom-info with no certificate in path specified by /etc/sysconfig/rhn/up2date in its sslCACert directive, an exception is raised about wrongly raised exception (raising a string rather than Exception object).

How reproducible:
Always

Steps to Reproduce:
1. rm $PATH_TO_CERT
2. rhn-custom-info -u admin -p pass -s https://${HOSTNAME}/rpc/api key val
Traceback (most recent call last):
  File "/usr/bin/rhn-custom-info", line 255, in <module>
    main()
  File "/usr/bin/rhn-custom-info", line 212, in main
    s = create_server_obj(url)
  File "/usr/bin/rhn-custom-info", line 81, in create_server_obj
    raise "could not find cert %s" % ca_cert
TypeError: exceptions must be old-style classes or derived from BaseException, not str

Actual results:
Exception about incorrectly raised exception

Expected results:
Exception about no cert found

Comment 2 Tomas Lestach 2018-04-09 15:25:36 UTC

We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.