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

Bug 1049283

Summary: [RFE][Admin Portal] VM removal should show events for removal of "child" components
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: iheim, jbelka, lpeer, ofrenkel, rbalakri, Rhev-m-bugs, sherold, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: sherold: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-22 15:46:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine.log none

Description Jiri Belka 2014-01-07 10:43:01 UTC
Created attachment 846577 [details]
engine.log

Description of problem:
VM removal does not show events for removal of "child" components.

I would expect to see events even for removal of network card, disk and then finalized by removal of the VM itself.

Version-Release number of selected component (if applicable):
is30 rhevm-3.3.0-0.43.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. add VM with network card, disk
2. remove VM
3. check Events

Actual results:
only event is for removal of VM itself

Expected results:
show events for removal of each "child" component (network card, disk...)

Additional info:

Comment 1 Omer Frenkel 2014-01-08 09:59:06 UTC
well not sure why this is relevant for the user,
its pretty obvious that if you remove the vm (and selected to remove the disks..) all its devices are removed, this may cause to flood the event log, in case of mass remove of vms, even with 2 disks and 1 nick each.
also when creating vm from template you get only 1 event for the vm, regardless to the number of devices the template has.

why do you think these extra event will be useful?

Comment 2 Jiri Belka 2014-01-08 16:33:53 UTC
I've thought its easier to map each specific events (add | remove). I can imagine some log checkers or searchers inside logs... Yes of course one can have some correlation engine which would do it... That's the reason why it has 'Low' priority.

And... FYI there is no difference in events if you delete a VM including disks and delete a VM not including disks -- it is just the same event:

2014-Jan-08, 17:24 VM obsd was successfully removed.

(I kept the disks). So RHEVM has to distinguish two types of VM removal.

How would an administrator know why there are disks ie. foobar1,foobar2 if foobar VM was delete 6 months ago? A bug in RHEVM code or somebody decided to keep disks?

And in storage events there is as well:

2014-Jan-08, 16:40 The disk obsd_Disk2 was successfully added to VM obsd.

But no info about obsd_Disk2 to be unlinked from VM (as the VM was deleted).

So the admin would have some disks on storage domain with little info why such disks exist there.

Comment 4 Itamar Heim 2015-03-22 15:46:27 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.