cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-4157) Failure to add zone wide primary storage pool is leaving storage pool in database
Date Wed, 07 Aug 2013 18:46:09 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Animesh Chaturvedi updated CLOUDSTACK-4157:
-------------------------------------------


These blockers and critical issues are resolved but not verified. Reporters of these issues
please verify the fixes and help close these issues
                
> 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

Mime
View raw message