cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9025) Unable to deploy VM instance from template if template spin from linked clone snapshot
Date Fri, 05 Jan 2018 13:06:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-9025:

DaanHoogland commented on a change in pull request #2315: A comprehensive solution for CLOUDSTACK-9025
and CLOUDSTACK-10128.

 File path: plugins/hypervisors/xenserver/src/com/cloud/hypervisor/
 @@ -167,35 +170,62 @@ public boolean trackVmHostChange() {
     public Pair<Boolean, Long> getCommandHostDelegation(long hostId, Command cmd) {
 Review comment:
   all the conditional returns compensate more then fully the complexity of the nested conditionals,
so i think the complexity grew. But of course you are right and we should actually measure
(lazy mode on - quickly)

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Unable to deploy VM instance from template if template spin from linked clone snapshot
> --------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-9025
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: XenServer
>    Affects Versions: 4.5.2
>         Environment: XenServer 6.5
>            Reporter: Anshul Gangwar
>            Assignee: Anshul Gangwar
>            Priority: Critical
>             Fix For: 4.6.0
> As default, CloudStack create linked clone snapshot for VM instance . When we take a
snapshot for the VM, and create a template based on such snapshot, CloudStack only download
incremental VHD as template file, as a result, the VM instance fail to deploy as it is incomplete.

This message was sent by Atlassian JIRA

View raw message