Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: serg38 <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
References: <git-pr-1813-cloudstack@git.apache.org>
In-Reply-To: <git-pr-1813-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack issue #1813: CLOUDSTACK-9604: Root disk resize support for VMware...
Content-Type: text/plain
Message-Id: <20170305170424.A6478DFBD9@git1-us-west.apache.org>
Date: Sun,  5 Mar 2017 17:04:24 +0000 (UTC)
archived-at: Sun, 05 Mar 2017 17:04:27 -0000

Github user serg38 commented on the issue:

    https://github.com/apache/cloudstack/pull/1813
  
    @borisstoyanov Thanks. Can you check in B.O. what is value of global configuration 'vmware.create.full.clone',  if the same configuration is set for the primary storage pool and if so what is the value ? 
    @priyankparihar Based on the exception it looks like B.O. Is set to use link clones but test doesn't handle it intended way.  How about you temporary alter 'vmware.create.full.clone' to make it true for the PS pool used during the test and then revert it back to the original value.
    You can use similar to below to alter flag just for the PS pool:
           updateConfigurationCmd = updateConfiguration.updateConfigurationCmd()
            updateConfigurationCmd.name = "vmware.create.full.clone"
            updateConfigurationCmd.value = "true"
            updateConfigurationCmd.storageid = pool.id
            updateConfigurationResponse = self.apiClient.updateConfiguration(updateConfigurationCmd)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---