[
https://issues.apache.org/jira/browse/CLOUDSTACK-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728448#comment-13728448
]
Rajesh Battala commented on CLOUDSTACK-3887:
--------------------------------------------
will work on it.
> [KVM] [PrimaryStorage] deleteStoragePool is not removing the storage pool
> information from KVM agent/host.
> ----------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3887
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3887
> 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: commit # ca474d0e09f772cb22abf2802a308a2da5351592
> Reporter: venkata swamybabu budumuru
> Assignee: Rajesh Battala
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce:
> 1. Have at least one advanced zone with KVM cluster of 2 hosts.
> 2. make sure everything is working fine.
> 3. add an additional primary storage with scope set to "Cluster"
> 4. verify and make sure that "#virsh pool-list & #virsh dump-xml <pool-id>"
> are showing the newly added one.
> 5. delete the above added primary storage from cloudstack.
> Observations:
> (i) I can see the deleteStoragePool API fired and went fine but, on the KVM
> host side, "virsh pool-list" still shows the primary storage that was added
> in 3rd step.
> (ii) I see that the HeartBeat is continuously written to the primary and it
> still considers that this primary is up.
> Attaching all the mgmt server, agent logs and db dump to the bug.
--
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
