Bug 876554 - rhevm-image-uploader with bad hostname/port give error message not clear to user.
Summary: rhevm-image-uploader with bad hostname/port give error message not clear to u...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-image-uploader
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.2.0
Assignee: Kiril Nesenko
QA Contact: Ilanit Stein
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-14 13:05 UTC by Ilanit Stein
Modified: 2014-07-11 00:09 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-24 09:47:49 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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