Bug 876554

Summary:	rhevm-image-uploader with bad hostname/port give error message not clear to user.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ilanit Stein <istein>
Component:	ovirt-image-uploader	Assignee:	Kiril Nesenko <knesenko>
Status:	CLOSED WONTFIX	QA Contact:	Ilanit Stein <istein>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.1.0	CC:	dfediuck, dyasny, iheim, mgoldboi, Rhev-m-bugs, sgrinber, ykaul
Target Milestone:	---
Target Release:	3.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-24 09:47:49 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:
Embargoed:

Description Ilanit Stein 2012-11-14 13:05:34 UTC

Description of problem:

For rhevm-image-uploader, using bad host name or port number,
in addition to a correct error [1]
There are 2 additional misleading messages:

1. [2] - Error unclear to user.
2. [3] - Info massage for how to run help is printed - no need for it since command syntax is OK.

console log:

[root@lilach-rhel tmp]# rhevm-image-uploader -u admin@internal  -r lilach-rhell.qa.lab.tlv.redhat.com:443 -e export_domain upload template.ovf 
Please provide the REST API password for the admin@internal RHEV-M user (CTRL+D to abort): 
[1]ERROR: Problem connecting to the REST API.  Is the service available and does the CA certificate exist?
[2]ERROR: 'NoneType' object is not iterable
[3]INFO: Use the -h option to see usage.

From bug 858968, by Keith Robertson:

The system upon which you are running the rhevm-image-uploader most likely does *not* have a valid CA certificate for lilach-rhel.qa.lab.tlv.redhat.com or you typed the PW wrong. The tool prints an appropriate error message [1]; however, there is a small bug that prints [2]. The root cause for [2] is that the code is expecting a 3 tuple but is receiving 'None' from the API creation code.