[
https://issues.apache.org/jira/browse/CLOUDSTACK-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754155#comment-13754155
]
ASF subversion and git services commented on CLOUDSTACK-4539:
-------------------------------------------------------------
Commit 07d79c7ad660375cfb0e88794048993c4e349cf0 in branch
refs/heads/4.2-forward from [~vijayendrabvs]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=07d79c7 ]
CLOUDSTACK-4539: [VMWARE] vmware.create.full.clone is set to true in upgraded
setup;default nature of vms are full clone
Reviwed-by: Kelven Yang <kelven.y...@citrix.com>
Description:
Change the criterion for overriding/preserving the vmware.create.full.clone
flag. The earlier criterion was simply the version numbers, but that is not
a good business logic basis for the change. With this fix, if past version
deployments have any deployments (data centers), this flag will be set to
false. Else, it will be set to true.
> [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
>
> Attachments: Logs_DB.rar
>
>
> 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
