[
https://issues.apache.org/jira/browse/CLOUDSTACK-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713566#comment-13713566
]
Rajesh Battala commented on CLOUDSTACK-3565:
--------------------------------------------
when user stop and starts (restart) the libvirtd,
Cloudstack agent will loose the connection with libvirtd.
2013-07-19 16:12:02,226 DEBUG [kvm.resource.LibvirtConnection]
(agentRequest-Handler-1:null) Connection with libvirtd is broken, due to Cannot
write data: Broken pipe
2013-07-19 16:12:02,377 DEBUG [cloud.agent.Agent] (agentRequest-Handler-3:null)
Processing command: com.cloud.agent.api.GetStorageStatsCommand
2013-07-19 16:12:02,492 DEBUG [kvm.resource.KVMHAMonitor] (Thread-16:null)
Failed to lookup libvirt storage pool f0802731-62fe-3a85-b81a-98ae47e845cf due
to: org.libvirt.LibvirtException: Storage pool not found: no pool with matching
uuid
[kvm.resource.KVMHAMonitor] (Thread-16:null) Failed to lookup libvirt storage
pool f0802731-62fe-3a85-b81a-98ae47e845cf due to: org.libvirt.LibvirtException:
Storage pool not found: no pool with matching uuid
2013-07-19 16:12:02,493 DEBUG [kvm.resource.KVMHAMonitor] (Thread-16:null)
removing pool from HA monitor since it was deleted
2013-07-19 16:12:02,493 DEBUG [utils.script.Script] (Thread-16:null) Executing:
/bin/bash -c umount /mnt/f0802731-62fe-3a85-b81a-98ae47e845cf
2013-07-19 16:12:02,537 DEBUG [utils.script.Script] (Thread-16:null) Exit value
is 16
2013-07-19 16:12:02,538 DEBUG [utils.script.Script] (Thread-16:null)
umount.nfs: /mnt/f0802731-62fe-3a85-b81a-98ae47e845cf: device is
busyumount.nfs: /mnt/f0802731-62fe-3a85-b81a-98ae47e845cf: device is busy
when the cloud agent is restarted, the pools are getting registered back.
Summary, when libvirtd got manually restarted, restart the cloudstack agent
also to set back the details.
> 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
