Bug 968961 - [User Portal] Displaying incorrect events after renaming VM
Summary: [User Portal] Displaying incorrect events after renaming VM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-userportal
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.4.0
Assignee: Oved Ourfali
QA Contact: movciari
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-30 11:29 UTC by movciari
Modified: 2015-09-22 13:09 UTC (History)
9 users (show)

Fixed In Version: ovirt-3.4.0-alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-12 14:05:50 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 23058 0 None None None Never

Description movciari 2013-05-30 11:29:37 UTC
Description of problem:
After you rename VM, its events will disappear from events subtab in userportal and there is only one event saying that it was renamed.
In webadmin events don't disappear

Another problem is that if you have VMs with names for example: "old" and "another", and you rename "old" to "new" and "another" to "old", then VM which currently has name "old" sees events generated for machine that previously had name "old"

Version-Release number of selected component (if applicable):
3.2.0-11.29 (sf17.2)

How reproducible:
Always

Steps to reproduce:
1: Rename VM
2: Go to events subtab of renamed VM in userportal

Actual results:
Only events generated after renaming VM are shown (including event that says VM was renamed)

Expected results:
All events generated before renaming VM should be shown too

Additional info:
It's working correctly in webadmin

Comment 2 Sandro Bonazzola 2014-01-14 08:43:57 UTC
ovirt 3.4.0 alpha has been released

Comment 3 Itamar Heim 2014-06-12 14:05:50 UTC
Closing as part of 3.4.0


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