[
https://issues.apache.org/jira/browse/CLOUDSTACK-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732204#comment-13732204
]
ASF subversion and git services commented on CLOUDSTACK-4157:
-------------------------------------------------------------
Commit 10c550e8caea8945951ab442bc3e424c2d34a376 in branch refs/heads/4.2 from
[~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=10c550e ]
CLOUDSTACK-4157 Failure to add zone wide primary storage pool is leaving
storage pool in database
Signed-off-by: Sateesh Chodapuneedi <[email protected]>
> Failure to add zone wide primary storage pool is leaving storage pool in
> database
> ---------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4157
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4157
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.2.0
> Reporter: Sateesh Chodapuneedi
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.2.0
>
>
> If creation of a zone wide primary storage pool is while attaching the
> storage pool to zone, cleanup should ensure the storage pool cleaned up from
> database as well. Currently primary storage is left in database even though
> none of the hosts of zone is attached to storage pool.
> This is observed for VMware as well as KVM.
--
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
