Bug 853227 - rhevm trys to run power management command on host during its installation
rhevm trys to run power management command on host during its installation
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Nobody's working on this, feel free to take it
Depends On:
  Show dependency treegraph
Reported: 2012-08-30 15:34 EDT by Rami Vaknin
Modified: 2016-02-10 14:43 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-12-01 04:59:03 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rami Vaknin 2012-08-30 15:34:32 EDT

I've installed few hosts using a rhevm-sdk based script that triggers their installation and configure power management right after installaiton starts.
I found in the log that rhevm failed to run a power management command for each of my installed hosts, rhevm tried to run that command during the installation of the hosts.

Reproduction steps:
1. Install a host or few hosts in parallel
2. Configure the host's power management during its installation using rhevm-sdk

From engine.log:
2012-08-30 22:13:34,780 INFO  [org.ovirt.engine.core.bll.UpdateVdsCommand] (ajp-/ [1ec2b6da] Running command: UpdateVdsCommand internal: false. Entities affected :  ID: 8eb698e6-f2e7-11e1-9ad2-03637d3562a9 Type: VDS
2012-08-30 22:13:35,180 ERROR [org.ovirt.engine.core.bll.FencingExecutor] (ajp-/ [1ec2b6da] Failed to run Power Management command on Host puma19, no running proxy Host was found.
Comment 1 Itamar Heim 2012-08-31 04:45:47 EDT
are we sure this isn't just trying to validate the PM configuration? log is missing which power management command was sent.
Comment 2 Rami Vaknin 2012-08-31 04:52:36 EDT
I assume that it is the command that validates the PM configuration, it just need to be running only after host is up and running or PM configuration should not be allowed during host installation - the first option is the preferred one.

I don't have a log of the PM command, but anyway I use the following code for PM configuration using rhevm-sdk:

host_obj = self.getSdkProxy().hosts.get(self.getName())
host_obj.power_management=params.PowerManagement(address='.'.join([self.getName() + c.PM_ADDRESS_ADDITION, self.getDomain()]), username=pm_user, password=pm_passwd, enabled='true', type_=pm_type)
Comment 4 Itamar Heim 2013-12-01 04:15:38 EST
eli - thoughts?
Comment 5 Eli Mesika 2013-12-01 04:45:34 EST
(In reply to Itamar Heim from comment #4)
> eli - thoughts?

When a Host is saved and have PM configured, the configuration is tested by sending a "status" command to the PM agent. 
In this case there is no Host in the Cluster or DC that can serve as a proxy and therefor the generated errors are OK and working as desgned.

Since that we are retring to find a proxy before giving up FindFenceProxyRetries times (3 by default) with delay of FindFenceProxyDelayBetweenRetriesInSec (30 sec by default) this mean that we didn't find a proxy for 90 sec before giving up.

I assume that with the new 3.3 Install procedure that don't require a Host reboot we will get those Hosts up withing those 90 sec and get a proxy as well, so I don't expect this BZ to be reproduced in 3.3
Comment 6 Itamar Heim 2013-12-01 04:59:03 EST
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.