Return-Path: 
 <issues-return-18025-apmail-cloudstack-issues-archive=cloudstack.apache.org@cloudstack.apache.org>
X-Original-To: apmail-cloudstack-issues-archive@www.apache.org
Delivered-To: apmail-cloudstack-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D997EC04B
	for <apmail-cloudstack-issues-archive@www.apache.org>;
 Mon, 29 Jul 2013 05:37:57 +0000 (UTC)
Received: (qmail 94581 invoked by uid 500); 29 Jul 2013 05:37:56 -0000
Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org
Received: (qmail 94534 invoked by uid 500); 29 Jul 2013 05:37:54 -0000
Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cloudstack.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cloudstack.apache.org>
List-Post: <mailto:issues@cloudstack.apache.org>
List-Id: <issues.cloudstack.apache.org>
Reply-To: dev@cloudstack.apache.org
Delivered-To: mailing list issues@cloudstack.apache.org
Received: (qmail 94516 invoked by uid 500); 29 Jul 2013 05:37:50 -0000
Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org
Received: (qmail 94505 invoked by uid 99); 29 Jul 2013 05:37:49 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jul 2013 05:37:49 +0000
Date: Mon, 29 Jul 2013 05:37:49 +0000 (UTC)
From: "venkata swamybabu budumuru (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12660317.1375073178573.126915.1375076269645@arcas>
In-Reply-To: <JIRA.12660317.1375073178573@arcas>
References: <JIRA.12660317.1375073178573@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-3887) [KVM] [PrimaryStorage]
 deleteStoragePool is not removing the storage pool information from KVM
 agent/host.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

venkata swamybabu budumuru updated CLOUDSTACK-3887:
---------------------------------------------------

    Attachment: logs.tgz
    
> [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
>            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