Bug 1182344 - [RFE] Provide more informative error messages for iso-uploader failures
Summary: [RFE] Provide more informative error messages for iso-uploader failures
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-iso-uploader
Version: 3.5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 3.6.0
Assignee: Lev Veyde
QA Contact: Gonza
URL:
Whiteboard: integration
Depends On:
Blocks: 1234840
TreeView+ depends on / blocked
 
Reported: 2015-01-14 22:27 UTC by Jake Hunsaker
Modified: 2015-11-04 13:54 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
the tool now provide more information on connection failures, so now more specific information will be available to users.
Clone Of:
Environment:
Last Closed: 2015-11-04 13:54:33 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 36929 0 master ABANDONED error handling: Provide more informative error messages Never
oVirt gerrit 42519 0 master MERGED ovirt-iso-uploader: Provide more informative error messages Never
oVirt gerrit 42554 0 master MERGED ovirt-image-uploader: Provide more informative error messages Never

Description Jake Hunsaker 2015-01-14 22:27:05 UTC
Description of problem:

Currently if any connection error is hit, the same message "is the service available and does the CA exist?", is displayed. 

There are several different reasons to hit a ConnectionError - and some imply we cannot hit the API while others imply we *can* but verification of the CA failed so we stopped.

Version-Release number of selected component (if applicable):
ovirt-iso-uploader-3.5.0-1

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
The same message is displayed for all failures


Expected results:
When possible, more informative error messages (such as where to check for problems) should be given. 

Additional info:

Comment 1 Yaniv Lavi 2015-04-07 09:16:32 UTC
should this be on POST?

Comment 2 Lev Veyde 2015-04-07 12:04:16 UTC
No, it's the correct status.

Comment 3 Gonza 2015-09-08 09:16:18 UTC
Verified with:
rhevm-iso-uploader-3.6.0-0.2.alpha.gitea4158a.el6ev.noarch

## Case with no network connection 
# engine-iso-uploader --conf-file=/tmp/isouploader.conf upload /tmp/cd57.iso 
ERROR: Problem connecting to the REST API at https://gr2.rhev.lab.eng.brq.redhat.com:443/api
[ERROR]::RHEV API connection failure, (7, "couldn't connect to host")

## Case with wrong ca.crt
# engine-iso-uploader --conf-file=/tmp/isouploader.conf upload /tmp/cd57.iso 
ERROR: Problem connecting to the REST API at https://gr2.rhev.lab.eng.brq.redhat.com:443/api
[ERROR]::RHEV API connection failure, (77, 'Problem with the SSL CA cert (path? access rights?)')

## Case with wrong login details
# engine-iso-uploader --conf-file=/tmp/isouploader.conf upload /tmp/cd57.iso 
ERROR: Unable to connect to REST API at https://gr2.rhev.lab.eng.brq.redhat.com:443/api
Host returned a 401 Unauthorized error.
Please check the provided username and password.

## Case with ovirt-engine service stopped
# engine-iso-uploader --conf-file=/tmp/isouploader.conf upload /tmp/cd57.iso 
ERROR: Unable to connect to REST API at https://gr2.rhev.lab.eng.brq.redhat.com:443/api
Host returned a 503 Service Unavailable error.
Please ensure the engine is running and the webUI is accessible.

Comment 4 Sandro Bonazzola 2015-11-04 13:54:33 UTC
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.


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