Bug 1478296 - Health check on Host <UNKNOWN> indicates that future attempts to Stop this host using Power-Management are expected to fail.
Summary: Health check on Host <UNKNOWN> indicates that future attempts to Stop this ho...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.1.4.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.1.7
: 4.1.7.1
Assignee: Miroslava Voglova
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-04 08:36 UTC by Jiri Belka
Modified: 2017-11-13 12:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-13 12:29:15 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 81905 0 ovirt-engine-4.1 MERGED core: add host name to power management alert 2020-07-30 13:17:27 UTC

Description Jiri Belka 2017-08-04 08:36:33 UTC
Description of problem:

Again odd 'UNKNOWN' in message, this time:

Health check on Host <UNKNOWN> indicates that future attempts to Stop this host using Power-Management are expected to fail.

I got only one host in the cluster. It's ok test fails but what is not ok is UNKNOWN, this is not nice.

Version-Release number of selected component (if applicable):
ovirt-engine-4.1.4.2-0.1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. add one host into DC/CL and define fencing for it
2. observe Alert tab in Admin Portal
3.

Actual results:
odd 'UNKNOWN' in message

Expected results:
UNKNOWN is not nice, seems like bad code

Additional info:

Comment 4 Petr Matyáš 2017-09-22 13:18:55 UTC
Verified on ovirt-engine-4.1.7.1-0.1.el7.noarch


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