cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sailaja Mada (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4038) State of the DATA volumes remains in Allocated state if they are deleted before using them (Attach/Detach)
Date Fri, 02 Aug 2013 10:03:49 GMT

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

Sailaja Mada commented on CLOUDSTACK-4038:
------------------------------------------

With this issue, Volumes details from list accounts is listed incorrectly. 

<volumelimit>20</volumelimit>
<volumetotal>-6</volumetotal>
<volumeavailable>26</volumeavailable>
                
> State of the DATA volumes remains in Allocated state if they are deleted before using
them (Attach/Detach) 
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4038
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4038
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller
>    Affects Versions: 4.2.0
>            Reporter: Sailaja Mada
>            Assignee: Likitha Shetty
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: apilog.log, clouddmp.sql, management-server.log
>
>
> Steps :
> 1. Configure Adv zone with VMWARE cluster 
> 2. Add new DATA volume with 5GB 
> 3. Delete this DATA volume  
> Observation :
> 1. There is a DB entry created for this volume when it is added 
> 2. Delete this volume without adding to any instance  ( Delete operations is passed)

> 3.  But state of the volume remains in Allocated in the database When its deleted before
attach/detach to the instance ,  
> 5. Its not removed by Storage GC also. 
> *************************** 17. row ***************************
>                         id: 17
>                 account_id: 4
>                  domain_id: 2
>                    pool_id: NULL
>               last_pool_id: NULL
>                instance_id: NULL
>                  device_id: NULL
>                       name: newvol
>                       uuid: 766f6e59-ffa4-4665-a237-0849cb5f9ee2
>                       size: 5368709120
>                     folder: NULL
>                       path: NULL
>                     pod_id: NULL
>             data_center_id: 2
>                 iscsi_name: NULL
>                    host_ip: NULL
>                volume_type: DATADISK
>                  pool_type: NULL
>           disk_offering_id: 3
>                template_id: NULL
> first_snapshot_backup_uuid: NULL
>                recreatable: 0
>                    created: 2013-08-02 08:11:18
>                   attached: NULL
>                    updated: 2013-08-02 08:11:18
>                    removed: NULL
>                      state: Allocated
>                 chain_info: NULL
>               update_count: 0
>                  disk_type: NULL
>             display_volume: 1
>                     format: NULL
>                   min_iops: NULL
>                   max_iops: NULL
>     vm_snapshot_chain_size: NULL
> *************************** 18. row ***************************

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