cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Tripathi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2143) Primary storage is not getting decremented when the instances are failed to deploy after the ROOT volume is created
Date Mon, 06 May 2013 11:20:17 GMT

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

Sanjay Tripathi commented on CLOUDSTACK-2143:
---------------------------------------------

If VM fails to deploy, it goes into error state and user can delete it (Root Volume) by calling
the destroyVM API command from the VM detailView window.

For VMs in error state, the storage count is getting decremented when user destroys that instance
so their is no need to "resource decrement" count in another place.
                
> Primary storage is not getting decremented when the instances are failed to deploy after
the ROOT volume is created
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2143
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2143
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: Setup : Advanced Networking Zone, Xen 6.1 , MS -RHel 6.3
>            Reporter: Sailaja Mada
>            Assignee: Sanjay Tripathi
>             Fix For: 4.2.0
>
>
> Steps:
> 1. Tried to deploy instance using ROOT Admin 
> 2. It failed to deploy instance as it failed to  copy the template from secondary to
primary But it had created the ROOT volume before this failure.
> 3. ROOT volume got deleted when deploy instance failed. 
> 4. Verify the primary storage usage using list accounts:  Note; Cpu & Memory got
decremented but not primary storage.
> http://localhost:8096/client/api?command=listAccounts&listAll=true 
> <cpulimit>Unlimited</cpulimit>
> <cputotal>1</cputotal>
> <cpuavailable>Unlimited</cpuavailable>
> <memorylimit>Unlimited</memorylimit>
> <memorytotal>512</memorytotal>
> <memoryavailable>Unlimited</memoryavailable>
> <primarystoragelimit>Unlimited</primarystoragelimit>
> <primarystoragetotal>105</primarystoragetotal>
> <primarystorageavailable>Unlimited</primarystorageavailable>

--
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

Mime
View raw message