[
https://issues.apache.org/jira/browse/CLOUDSTACK-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753168#comment-13753168
]
ASF subversion and git services commented on CLOUDSTACK-4539:
-------------------------------------------------------------
Commit a30a33c14d38a30840be19619c9aff65ed14cf2f in branch
refs/heads/4.2-forward from [~vijayendrabvs]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a30a33c ]
CLOUDSTACK-4539: [VMWARE] vmware.create.full.clone is set to true in upgraded
setup;default nature of vms are full clone
Description:
Do not overwrite value of vmware.create.full.clone flag in the
cloud db if it already exists. This will preserve the configured
clone creation behaviour across upgrades.
> [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
