Bug 787623 - [webadmin]-[PM] No error message when entering wrong PM settings or no other proxy is available
Summary: [webadmin]-[PM] No error message when entering wrong PM settings or no other ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Einav Cohen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-06 11:02 UTC by zvi
Modified: 2016-01-28 21:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-06 11:25:41 UTC
oVirt Team: ---


Attachments (Terms of Use)

Description zvi 2012-02-06 11:02:13 UTC
Description of problem:

when configuring an Host with wrong PM settings, or when there is no Host Proxy, a message is shown in BE log, that should be reflected in webadmin. 

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


How reproducible:
Always

Steps to Reproduce:
1.Configure an Host with wrong params and press the OK button / Or configure PM when there is only one Host in the  Cluster.
2.
3.

Actual results:
No Error message.

Expected results:

The BE error message should be reflected via an error message.

Additional info:
No proxy:

fected :  ID: cf51fd24-50a7-11e1-a45a-001a4a169746 Type: VDS
2012-02-06 12:47:57,357 ERROR [org.ovirt.engine.core.bll.FencingExecutor] (http--0.0.0.0-8080-8) Failed to run Power Management command on Host navy-vds1.qa.lab.tlv.redhat.com, no running proxy Host was found.





only one Host:

Comment 1 Einav Cohen 2012-02-06 11:25:41 UTC
The action of saving the Host PM configuration has succeeded, this is why there is no error that is being reflected in the web-admin.

The PM itself might be configured wrongly; in order to find out whether the PM is configured wrongly or not, you have the "Test" button in the New/Edit Host dialog.

If you haven't Tested explicitly the PM configuration and saved the Host as is, saving will succeed; the backend might perform the testing for you behind the scenes in this case; if this test fails, you will see an Event/Alert at the bottom of the application.


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