Bug 784290 - oVirt-Engine-Logcollector - Too many Failure messages when writing wrong API User Name [TXT]
Summary: oVirt-Engine-Logcollector - Too many Failure messages when writing wrong API ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-logcollector
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Barak
QA Contact:
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-24 13:37 UTC by Ortal
Modified: 2012-12-17 07:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-17 07:26:12 UTC
oVirt Team: ---


Attachments (Terms of Use)

Description Ortal 2012-01-24 13:37:21 UTC
Description of problem:

oVirt-Engine-Logcollector - Too many Failure messages when writing wrong API User Name

Version-Release number of selected component (if applicable):
ovirt-engine-log-collector-3.0.0_0001-1.3.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open new shell to your oVirt machine and run: engine-log-collector list
2. Wnter wrong username or Password
  
Actual results:


[root@zvi-upstream ~]# engine-log-collector list
Please provide the REST API username for oVirt Engine (CTRL+D to skip): admin
Please provide the REST API password for the admin oVirt Engine user (CTRL+D to skip):
ERROR: _fetch_from_api: Failure while fetching https://localhost:8443/api/datacenters: HTTP Error 401: Unauthorized
ERROR: _fetch_from_api: Failure while fetching https://localhost:8443/api/hosts: HTTP Error 401: Unauthorized
ERROR: _fetch_from_api: Failure while fetching https://localhost:8443/api/clusters: HTTP Error 401: Unauthorized
ERROR: get_all: Failed to get hosts from ENGINE. Did the API calls fail?
INFO: No hypervisors were found, therefore no hypervisor data will be listed.


Expected results:

Need to see only one Failure message and not five.

** According to Kieth:
"I am beginning to think that the error message I display there is terrible.  Hindsight being 20/20 coupled with the fact that I now see how people actually use the tool I think that I can do better.  If you write me a BZ on it I'll try to clean it up somehow.  I'm not exactly sure what I'm going to do because there are a *lot* of HTTP error codes and sometimes the same code has multiple meanings.  As such, it isn't really feasible to create a mapping for every possible problem to a remedy string."

Comment 1 Ortal 2012-01-24 13:37:54 UTC
**** The same result for engine-iso-uploader

Comment 2 Itamar Heim 2012-12-17 07:26:12 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.


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