Koushik Das c69da4c1b3 CLOUDSTACK-595 : Recreate root volume scenarios doesn't work in vmware ... Issue seen during system vm template upgrade and restoreVM command scenarios for vmware. In these cases CS tries to recreate root disk with same name as the existing one, in case of vmware this results in creation of vmdk file with same name for both existing and new root volume. This results in undesired behavior when storage cleanup thread tries to cleanup old volume. Made the vmdk file name unique by adding the volume id to it. This will ensure that during volume recreation in the scenarios mentioned vmdk will get created with a new name and there will be no undesired side effects of running the storage cleanup thread.		2013-01-07 16:08:04 +05:30
..
deployment-planners	CLOUDSTACK-580 setting all (I think) of the versions to 4.0.1-incubating	2012-12-06 13:52:27 -05:00
file-systems/netapp	apparently I missed some versions - CLOUDSTACK-580	2012-12-06 14:30:00 -05:00
host-allocators/random	CLOUDSTACK-580 setting all (I think) of the versions to 4.0.1-incubating	2012-12-06 13:52:27 -05:00
hypervisors	CLOUDSTACK-595 : Recreate root volume scenarios doesn't work in vmware	2013-01-07 16:08:04 +05:30
network-elements	CLOUDSTACK-699: removing hard-coded references to 4.0.0-incubating/changing to 4.0.1-incubating.	2013-01-04 15:37:15 -06:00
storage-allocators/random	CLOUDSTACK-580 setting all (I think) of the versions to 4.0.1-incubating	2012-12-06 13:52:27 -05:00
user-authenticators	CLOUDSTACK-580 setting all (I think) of the versions to 4.0.1-incubating	2012-12-06 13:52:27 -05:00
pom.xml	CLOUDSTACK-580 setting all (I think) of the versions to 4.0.1-incubating	2012-12-06 13:52:27 -05:00