[
https://issues.apache.org/jira/browse/CLOUDSTACK-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690298#comment-13690298
]
Koushik Das commented on CLOUDSTACK-3083:
-----------------------------------------
1. Simply adding a volume shouldn't consider the space availability in the
storage pool as it is not actually created in the pool till you attach it to a
VM. The user may not even attach it to a VM or may do so after removing
existing volumes.
2. There can be multiple pools available, which gets determined by the planner
when the attach volume happens. Also one may choose to add another primary
storage pool after adding the volume.
Based on the above, I see no reason to check for pool capacity at the time of
adding volumes.
> create volume doesn't check Global parameter "
> pool.storage.capacity.disablethreshold"
> --------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3083
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3083
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Storage Controller
> Affects Versions: 4.2.0
> Reporter: prashant kumar mishra
> Assignee: Koushik Das
> Fix For: 4.2.0
>
> Attachments: Logs_Db.rar, Logs_DB.rar
>
>
> Steps to reproduce
> ----------------------------
> 1-Set GP "pool.storage.capacity.disablethreshold" to 0
> 2-restart MS
> 3-Add a volume (Storage-->add volume)
> Expected
> ----------------
> Add volume should fail
> Actual
> -------------
> Addition of volume went successfully
--
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
