I think it seems easy to rename the mount when registering the pool, either the old one (if that works) or the new one. Yes, HA has a bad habit of remounting primary nfs in certain circumstances too. On Sep 16, 2013 11:47 AM, "Wei Zhou (JIRA)" <j...@apache.org> wrote:
> > [ > https://issues.apache.org/jira/browse/CLOUDSTACK-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768543#comment-13768543] > > Wei Zhou commented on CLOUDSTACK-3565: > -------------------------------------- > > Marcus, Thanks for your reply. > As Edison committed for CLOUDSTACK-4405 (the issue exists in 4.1 as well), > he added a libvirt hook so libvirt is needed to restart. > If storage pool is not persistent, it may take very long time to upgrade > cloudstack and fix the issue. > In libvirt, the define/create of storage pool will fail if the mountpoint > is already mounted (I tested in 0.9.13 and 0.10.2). > I will have a look the patches for CLOUDSTACK-3535 to see if the storage > pool affect the HA or not. > > > 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: Marcus Sorensen > > Priority: Blocker > > Labels: documentation > > 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 >
