Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1501455

Summary: Failed to verify power management agent
Product: [oVirt] ovirt-engine Reporter: Petr Matyáš <pmatyas>
Component: BLL.InfraAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, emesika, oourfali, pmatyas
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:39:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine log none

Description Petr Matyáš 2017-10-12 15:21:50 UTC
Created attachment 1337841 [details]
engine log

Description of problem:
When activating host from maintenance I get failed event about failing to verify power management agent, however this host got 'Test successful: power on' when adding it. Also fence operations (restart) works fine.

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20171011115800.git3cda941.el7.centos.noarch

How reproducible:
always

Steps to Reproduce:
1. add a new host with PM agent
or
1. put host with PM agent to maintenance
2. activate that host

Actual results:
failed to verify power management agent

Expected results:
PM verification works properly

Additional info:

Comment 1 Martin Perina 2017-10-13 09:32:11 UTC
Could you please upload full engine log?

Comment 8 Petr Matyáš 2017-11-06 16:51:24 UTC
Verified on ovirt-engine-4.2.0-0.0.master.20171105155215.git59d3324.el7.centos.noarch

Comment 9 Sandro Bonazzola 2017-12-20 11:39:49 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.