Bug 720687 - [vdsm] Deletion of template on one domain removes template from all domains
Summary: [vdsm] Deletion of template on one domain removes template from all domains
Keywords:
Status: CLOSED DUPLICATE of bug 718715
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.1
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Dan Kenigsberg
QA Contact: Jakub Libosvar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-12 13:52 UTC by Jakub Libosvar
Modified: 2011-07-12 14:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-12 14:24:55 UTC
Target Upstream Version:


Attachments (Terms of Use)
vdsm log (67.20 KB, application/octet-stream)
2011-07-12 13:52 UTC, Jakub Libosvar
no flags Details

Description Jakub Libosvar 2011-07-12 13:52:38 UTC
Created attachment 512431 [details]
vdsm log

Description of problem:
When user has template on two domains (copied) and wants to remove from one domain, template is erased on all domains.

Version-Release number of selected component (if applicable):
vdsm-4.9-79.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Have two storage data domains and template which resides on both domains
2. Erase template from one storage (Template tab, click template, Storage subtab)
  
Actual results:
Template is erased from all domains and is unusable, unremovable 

Expected results:
Template is erased only from selected domain

Additional info:
deleteImage is called only on relevant domain f11112ac-e57c-4ba0-8115-cf50eb4bd66a
Thread-5707::INFO::2011-07-12 15:41:20,321::dispatcher::94::Storage.Dispatcher.Protect::(run) Run and protect: deleteImage, args: ( sdUUID=f11112ac-e57c-4ba0-8115-cf50eb4bd66a spUUID=4be464f1-04a3-43d4-8bf4-03d0682dbfa5 imgUUID=6bd57739-87b4-4e75-af4b-e96ab540317c postZero=false force=false)

lvremove too:
Thread-5707::DEBUG::2011-07-12 15:41:23,239::lvm::359::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm lvremove --config " devices { preferred_names = [\\"^/dev/mapper/\\"] ignore_suspended_devices=1 write_cache_state=0 filter = [ \\"a%/dev/mapper/1IET_00040001|/dev/mapper/1IET_00040002|/dev/mapper/1IET_00040003|/dev/mapper/1IET_00040004|/dev/mapper/1IET_00040005|/dev/mapper/1IET_00040006|/dev/mapper/1IET_00040007|/dev/mapper/1IET_00040008|/dev/mapper/1IET_00040009|/dev/mapper/1IET_0004000a|/dev/mapper/1IET_0004000b|/dev/mapper/1IET_0004000c|/dev/mapper/1IET_0004000d|/dev/mapper/1IET_0004000e|/dev/mapper/1IET_0004000f|/dev/mapper/1IET_00040010|/dev/mapper/1IET_00040011|/dev/mapper/1IET_00040012|/dev/mapper/1IET_00040013|/dev/mapper/1IET_00040014|/dev/mapper/1IET_00040015|/dev/mapper/1IET_00040016|/dev/mapper/1IET_00040017|/dev/mapper/1IET_00040018|/dev/mapper/1IET_00040019|/dev/mapper/1IET_0004001a|/dev/mapper/1IET_0004001b|/dev/mapper/1IET_0004001c|/dev/mapper/1IET_0004001d|/dev/mapper/1IET_0004001e|/dev/mapper/1IET_0004001f|/dev/mapper/1IET_00040020|/dev/mapper/1IET_00040021|/dev/mapper/1IET_00040022|/dev/mapper/1IET_00040023|/dev/mapper/1IET_00040024|/dev/mapper/1IET_00040025|/dev/mapper/1IET_00040026|/dev/mapper/1IET_00040027|/dev/mapper/1IET_00040028|/dev/mapper/1IET_00040029|/dev/mapper/1IET_0004002a|/dev/mapper/1IET_0004002b|/dev/mapper/1IET_0004002c|/dev/mapper/1IET_0004002d|/dev/mapper/1IET_0004002e|/dev/mapper/1IET_0004002f|/dev/mapper/1IET_00040030|/dev/mapper/1IET_00040031|/dev/mapper/1IET_00040032|/dev/mapper/1jlibosva1|/dev/mapper/1jlibosva2%\\", \\"r%.*%\\" ] }  global {  locking_type=1  prioritise_write_locks=1  wait_for_locks=1 }  backup {  retain_min = 50  retain_days = 0 } " -f --autobackup n f11112ac-e57c-4ba0-8115-cf50eb4bd66a/fcbaf706-db08-4cb7-b875-a87829900ede' (cwd None)


Relevant vdsm log attached

It's a regression. I remember how happy I was when this feature was implemented.

Comment 1 Jakub Libosvar 2011-07-12 13:57:50 UTC
I think problem is that the whole LV is removed. On the second domain where template should remain actually is the image, but link points nowhere: 
fcbaf706-db08-4cb7-b875-a87829900ede -> /dev/e163fa82-dc74-4170-98d2-7867d82068f9/fcbaf706-db08-4cb7-b875-a87829900ede

Comment 2 Jakub Libosvar 2011-07-12 13:58:50 UTC
Hmm, bugzilla doesn't show my red marked links. The lv device doesn't exist
ls /dev/e163fa82-dc74-4170-98d2-7867d82068f9/fcbaf706-db08-4cb7-b875-a87829900ede
ls: cannot access /dev/e163fa82-dc74-4170-98d2-7867d82068f9/fcbaf706-db08-4cb7-b875-a87829900ede: No such file or directory

Comment 4 Itamar Heim 2011-07-12 14:17:55 UTC
duplicate of bug 718715?

Comment 5 Jakub Libosvar 2011-07-12 14:24:55 UTC
Yes, it is

*** This bug has been marked as a duplicate of bug 718715 ***


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