Bug 817366 - ovirt-engine-backend [Task Manager]: when removing a pool the cluster name appears in the task as "VdsGroups"
Summary: ovirt-engine-backend [Task Manager]: when removing a pool the cluster name ap...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Omer Frenkel
QA Contact: Dafna Ron
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-29 12:38 UTC by Dafna Ron
Modified: 2015-10-27 23:58 UTC (History)
9 users (show)

Fixed In Version: SI6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 20:06:05 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
log and screen shot (84.08 KB, application/x-gzip)
2012-04-29 12:38 UTC, Dafna Ron 		no flags Details
View All

Description Dafna Ron 2012-04-29 12:38:11 UTC 
Created attachment 581062 [details]
log and screen shot

Description of problem:

when removing a pool the task appears in the task manager with cluster name "VdsGroups" instead of actual cluster name. 

	
2012-Apr-29, 15:24:05
	
Removing VM Pool TEST from Cluster VdsGroups

Version-Release number of selected component (if applicable):

si2.1

How reproducible:

100%

Steps to Reproduce:
1. create a pool
2. detach the vm's
3. remove the pool
  
Actual results:

task shows cluster name as "VdsGroups" instead of actual cluster name 

Expected results:

we should see cluster name or generic cluster name as we see for vm's: 
	
Removing VM TEST-10 from system

Additional info: screen shot and log
Comment 1 Omer Frenkel 2012-05-21 11:54:42 UTC 
http://gerrit.ovirt.org/#change,4612
Comment 2 Omer Frenkel 2012-05-22 08:56:38 UTC 
gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=08d7274ee936db8e8c399ad7de3f9b0cd42d1f57
Comment 3 Dafna Ron 2012-06-14 13:38:01 UTC 
verified on si6

Removing VM Pool-1 from system
Note You need to log in before you can comment on or make changes to this bug.