[
https://issues.apache.org/jira/browse/CLOUDSTACK-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758270#comment-13758270
]
ASF subversion and git services commented on CLOUDSTACK-4539:
-------------------------------------------------------------
Commit 57dc52bb6f04c6e6c92a90282d9c88c5db741c23 in branch refs/heads/master
from [~vijayendrabvs]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=57dc52b ]
CLOUDSTACK-4539: [VMWARE] vmware.create.full.clone is set to true in upgraded
setup;default nature of vms are full clone
Description:
Set the criterion for overriding/preserving the vmware.create.full.clone
flag so that if past version deployments have any deployments (data
centers),
this flag will be set to false. Else, it will be set to true.
The earlier criterion to set this flag was based on the CS version numbers,
but that is not a good business logic to serve as a basis to set the flag.
> [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
