Bug 1389184 - [UI] - VM name is <UNKNOWN> in the event log when shutting a VM down
Summary: [UI] - VM name is <UNKNOWN> in the event log when shutting a VM down
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.1.0
Hardware: x86_64
OS: Linux
unspecified
low vote
Target Milestone: ovirt-4.1.0-beta
: ---
Assignee: Shmuel Melamud
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-27 06:40 UTC by Michael Burman
Modified: 2017-01-15 19:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-15 19:29:08 UTC
oVirt Team: Virt
rule-engine: ovirt-4.1?
ykaul: blocker+
mburman: planning_ack?
mburman: devel_ack?
mburman: testing_ack?

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

Description Michael Burman 2016-10-27 06:40:00 UTC 
Created attachment 1214499 [details]
screenshot

Description of problem:
[UI] - VM name is <UNKNOWN> in the event log ui when shutting a VM down 

- VM <UNKNOWN> is down. Exit message: Admin shut down from the engine

Version-Release number of selected component (if applicable):
4.1.0-0.0.master.20161025231555.gitf10966b.el7.centos
Comment 1 Tomas Jelinek 2016-12-14 14:51:05 UTC 
another incarnation similar to https://bugzilla.redhat.com/show_bug.cgi?id=1395602 and https://bugzilla.redhat.com/show_bug.cgi?id=1395606
Comment 2 Red Hat Bugzilla Rules Engine 2016-12-27 16:39:43 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 3 Shmuel Melamud 2017-01-15 19:29:08 UTC 
Cannot reproduce on the current ovirt-engine-4.1 branch. Most likely was fixed by this patch: https://gerrit.ovirt.org/69311/.
Note You need to log in before you can comment on or make changes to this bug.