You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rayees Namathponnan (JIRA)" <ji...@apache.org> on 2013/07/16 23:22:50 UTC
[jira] [Created] (CLOUDSTACK-3565) Restarting libvirtd service
leading to destroy storage pool
Rayees Namathponnan created CLOUDSTACK-3565:
-----------------------------------------------
Summary: 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
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