Bug 1389173 - [UI] - Host name is <UNKNOWN> in the event log
Summary: [UI] - Host name is <UNKNOWN> in the event log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.1.0
Hardware: x86_64
OS: Linux
unspecified
low vote
Target Milestone: ovirt-4.1.0-alpha
: 4.1.0
Assignee: Allon Mureinik
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-27 06:05 UTC by Michael Burman
Modified: 2017-02-01 14:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-01 14:46:26 UTC
oVirt Team: Infra
rule-engine: ovirt-4.1+
rule-engine: blocker+
rule-engine: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)
screenshot (138.58 KB, image/png)
2016-10-27 06:05 UTC, Michael Burman 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 65725 0 None None None 2016-11-01 16:50:40 UTC
oVirt gerrit 65769 0 None None None 2016-11-01 16:51:12 UTC

Description Michael Burman 2016-10-27 06:05:20 UTC 
Created attachment 1214491 [details]
screenshot

Description of problem:
[UI] - Host name is <UNKNOWN> in the event log

The host name is UNKNOWN in the event log ui for the next scenarios -

1) Host <UNKNOWN> is non responsive.
2) Host <UNKNOWN> is not responding. Host cannot be fenced automatically because power management for the host is disabled.
3) Host <UNKNOWN> became non responsive. It has no power management configured. Please check the host status, manually reboot it, and click "Confirm Host Has Been Rebooted"
4) Status of host <UNKNOWN> was set to Up.
5) Storage Pool Manager runs on Host <UNKNOWN> (Address: camel-vdsa.qa.lab.tlv.redhat.com).
6)  Failed to verify Power Management configuration for Host <UNKNOWN>.


Version-Release number of selected component (if applicable):
4.1.0-0.0.master.20161025231555.gitf10966b.el7.centos

It's a regression from previous builds.
Comment 1 Red Hat Bugzilla Rules Engine 2016-10-30 14:31:14 UTC 
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 2 Eli Mesika 2016-10-31 12:08:08 UTC 
I saw that there was a big re-factoring over the audit log classes by Allon M 
I have checked out the commit before those changes were applied 0f99715847cefdb5c102d251d31b2cb5f8b69f52

In that commit, the right host name is displayed for the above messages.

Allon, can you look at that and recommend how to solve ?
Comment 3 Allon Mureinik 2016-11-01 16:50:40 UTC 
It's impossible to say anything useful without the logs, but I'm unable to reproduce on latest master after 2d9dc86 and 65725 were applied.

Moving to MODIFIED to be verified on the next build.
Comment 4 Sandro Bonazzola 2016-12-12 13:54:01 UTC 
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.
Comment 5 Jiri Belka 2017-01-11 14:25:53 UTC 
what are reproduce/verification steps? unfortunatelly #0 misses description how to get such events.
Comment 6 Michael Burman 2017-01-11 14:47:10 UTC 
Hi Jiri

Make host non-responsive
Comment 7 Michael Burman 2017-01-18 06:34:25 UTC 
Verified on - 4.1.0-0.3.beta2.el7 and 4.1.0-0.4.master.20170117182028.git4678f8c.el7.centos
Note You need to log in before you can comment on or make changes to this bug.