[
https://issues.apache.org/jira/browse/CLOUDSTACK-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753438#comment-13753438
]
prashant kumar mishra edited comment on CLOUDSTACK-4539 at 8/29/13 8:51 AM:
----------------------------------------------------------------------------
i tested in upgraded setup, default value for vmware.create.full.clone =true
and vms are coming as full clone attaching logs and BD dump
Build info
=========
commit :995e193be2a1aad8ffe0eeb03357e23fb5c63769 ;
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=995e193be2a1aad8ffe0eeb03357e23fb5c63769
was (Author: prashantkm):
i tested in upgraded setup, default value for vmware.create.full.clone
=true and vms are comming as full clone attach8ing logs and BD dump
> [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default
> nature of vms are full clone
> -------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4539
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4539
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.2.0
> Reporter: prashant kumar mishra
> Assignee: Venkata Siva Vijayendra Bhamidipati
> Priority: Critical
> Fix For: 4.2.0, 4.2.1
>
>
> In upgraded setup vm should get deployed as linked clone ,default value of
> global parameter vmware.create.full.clone should be false in upgraded setup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
