Bug 1156122 - No error message on authentication error from optimizer
Summary: No error message on authentication error from optimizer
Keywords:
Status: CLOSED DUPLICATE of bug 1140293
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-optimizer
Version: 3.5.0
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Martin Sivák
QA Contact: Lukas Svaty
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-23 15:31 UTC by Lukas Svaty
Modified: 2016-02-10 20:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-26 15:29:46 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukas Svaty 2014-10-23 15:31:37 UTC
Description of problem:
When authentication from ovirt-optimizer fails (for example on incorrect password) no error is displayed in engine ui plugin.

Version-Release number of selected component (if applicable):
vt7

How reproducible:
100%

Steps to Reproduce:
1. Set up ovirt optimizer
2. put wrong password to /etc/ovirt-optimizer/ovirt-optimizer.properties
3. See status in engine webadmin portal clusters/ovirt-optimizer

Actual results:
Status: Solution received
No VM starts are requested at this moment.

Expected results:
Status: Authentication error


Additional info:
console.log of optimizer:
17:30:36,832 ERROR [org.ovirt.optimizer.service.OptimizerServiceBean] (http-/0.0.0.0:8080-1) Cluster 00000001-0001-0001-0001-000000000024 does not exist
17:30:36,833 INFO  [stdout] (http-/0.0.0.0:8080-1) 2014-10-23 17:30:36,832 ERROR [org.ovirt.optimizer.service.OptimizerServiceBean] Cluster 00000001-0001-0001-0001-000000000024 does not exist

it would be good to reflect this issue in webadmin portal (if possible)

Comment 1 Doron Fediuck 2014-10-26 15:29:46 UTC
This should be resolved as a prt of bug 1140293.

*** This bug has been marked as a duplicate of bug 1140293 ***


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