Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1057208 - Incomprehensible error when testing power management
Summary: Incomprehensible error when testing power management
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.4.0
Assignee: Eli Mesika
QA Contact:
Whiteboard: infra
Depends On:
TreeView+ depends on / blocked
Reported: 2014-01-23 15:56 UTC by Lior Vernia
Modified: 2015-05-05 01:44 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-02-23 21:23:47 UTC
oVirt Team: ---

Attachments (Terms of Use)

Description Lior Vernia 2014-01-23 15:56:11 UTC
Description of problem:

Having one host in the cluster WITHOUT power management configured, and then trying to add a new one WITH power management, it fails miserably when testing it without explaining the reason.

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

oVirt 3.4 beta.

How reproducible:

Not very, start with a clean setup.

Steps to Reproduce:
1. Add new host without power management.
2. Add new host with power management, and click the test button.

Actual results:

Failure with an unenlightening error message (don't have access to it anymore, but something about network connection error).

Expected results:

Success if possible, or at least an error message telling the user what the problem was (e.g. at least two hosts have to be configured with power management in the cluster or something of the sort).

Additional info:

Not 100% reproducible, happened to me on a clean setup but not since. Existing host was a Fedora host that possibly was in maintenance, new host being added was el-6.5.

Comment 1 Eli Mesika 2014-02-10 14:41:19 UTC

1) Did you wait for the Host deploy process to complete before pushing the TEST button , it seems that you failed to connect to the Host that was supposed to be 6the proxy for the fencing operations 

2) engine + vdsm logs please

Comment 2 Eli Mesika 2014-02-23 21:23:47 UTC
Closed on insufficient data , if you think this is still relevant please provide needed info and logs please

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