[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754162#comment-13754162
 ] 

Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4539:
-----------------------------------------------------------------

Hi Prashant,

I discussed this bug with Kelven/Alex/Will. Alex was of the view that merely 
shifting from one version to the next should not be the criterion for updating 
this flag. The business case would be to set this flag to false if deployments 
(data centers) already exist on the setup, and true otherwise. I've made the 
changes appropriately. So, when you test this, you will have three scenarios:

1) Upgrade from 3.0.6 that has no data centers created in it, to 4.2, and the 
flag must be set to true post upgrade.
2) Upgrade from 3.0.6 that has data centers created in it, to 4.2, and the flag 
must be set to false post upgrade.
3) Deploy a fresh 4.2.0 setup, and the flag must be set to true post deployment.

The VMs should get created accordingly.

Thanks,
Regards,
Vijay
                
> [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

Reply via email to