Return-Path: 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 51ADE10B4C for ; Thu, 18 Jul 2013 12:36:51 +0000 (UTC) Received: (qmail 37573 invoked by uid 500); 18 Jul 2013 12:36:50 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 37553 invoked by uid 500); 18 Jul 2013 12:36:50 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 37534 invoked by uid 500); 18 Jul 2013 12:36:50 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 37523 invoked by uid 99); 18 Jul 2013 12:36:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jul 2013 12:36:49 +0000 Date: Thu, 18 Jul 2013 12:36:48 +0000 (UTC) From: "Wei Zhou (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-3565) Restarting libvirtd service leading to destroy storage pool 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-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712276#comment-13712276 ] Wei Zhou commented on CLOUDSTACK-3565: -------------------------------------- yep. When Agent start, it will receive and process ModifyStoragePoolCommand which get the existing storage pool or create a storage pool if not exists. Actually, a pool should be in the pool-list if any VM in the pool is running. > Restarting libvirtd service leading to destroy storage pool > ----------------------------------------------------------- > > Key: CLOUDSTACK-3565 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3565 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: KVM > Affects Versions: 4.2.0 > Environment: KVM > Branch 4.2 > Reporter: Rayees Namathponnan > Assignee: Rajesh Battala > Priority: Blocker > Fix For: 4.2.0 > > > Steps to reproduce > Step 1 : Create cloudstack step in kvm > Step 2 : From kvm host check "virsh pool-list" > Step 3: Stop and start libvirtd service > Step 4 : Check "virsh pool-list" > Actual Result > "virsh pool-list" is blank after restart libvird service > [root@Rack2Host12 agent]# virsh pool-list > Name State Autostart > ----------------------------------------- > 41b632b5-40b3-3024-a38b-ea259c72579f active no > 469da865-0712-4d4b-a4cf-a2d68f99f1b6 active no > fff90cb5-06dd-33b3-8815-d78c08ca01d9 active no > [root@Rack2Host12 agent]# service cloudstack-agent stop > Stopping Cloud Agent: > [root@Rack2Host12 agent]# virsh pool-list > Name State Autostart > ----------------------------------------- > 41b632b5-40b3-3024-a38b-ea259c72579f active no > 469da865-0712-4d4b-a4cf-a2d68f99f1b6 active no > fff90cb5-06dd-33b3-8815-d78c08ca01d9 active no > [root@Rack2Host12 agent]# virsh list > Id Name State > ---------------------------------------------------- > [root@Rack2Host12 agent]# service libvirtd stop > Stopping libvirtd daemon: [ OK ] > [root@Rack2Host12 agent]# service libvirtd start > Starting libvirtd daemon: [ OK ] > [root@Rack2Host12 agent]# virsh pool-list > Name State Autostart > ----------------------------------------- -- 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