You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Likitha Shetty (JIRA)" <ji...@apache.org> on 2013/08/16 12:00:47 UTC
[jira] [Resolved] (CLOUDSTACK-4352) [VMWARE]Resize of offline
(Detached} volumes to the same size is allowed from Cloudstack with which
worker VM's are not getting deleted from VMWARE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Likitha Shetty resolved CLOUDSTACK-4352.
----------------------------------------
Resolution: Fixed
> [VMWARE]Resize of offline (Detached} volumes to the same size is allowed from Cloudstack with which worker VM's are not getting deleted from VMWARE
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4352
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4352
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Storage Controller, VMware
> Affects Versions: 4.2.0
> Reporter: Sailaja Mada
> Assignee: Likitha Shetty
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: apilog.log, dbdmp.sql, management-server.log, resizevols.png
>
>
> Steps:
> 1. Configure Adv Zone with VMWARE
> 2. Deploy VM
> 3. Attach new DATA volume of 5 GB to this instance
> 4. Detach the DATA volume
> 5. Resize the volume to same size as 5 GB
> Observation:
> 1. Now we allow to resize offline volumes after the fix for : CLOUDSTACK-4143) [VMWARE] Resize request sent for the volumes which are not attached to the instance
> 2. This fix will create worker VM when requested to resize offline volumes and gets deleted after resize is completed
> 3. But Resize of offline (Detached} volumes to the same size is allowed from Cloudstack with which worker VM's are not getting deleted from VMWARE
--
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