Re: Orphaned libvirt storage pools

2013-06-12 Thread Wido den Hollander
Hi Wei, This was with both 0.9.8 as with 1.0.2 Haven't been able to dig into this deeper yet. Wido On 06/12/2013 06:26 PM, Wei ZHOU wrote: Wido, Could you tell me the libvirt version? For our platform with this issue, the libvirt version is 0.9.13 -Wei 2013/6/7 Marcus Sorensen There is

Re: Orphaned libvirt storage pools

2013-06-12 Thread Wei ZHOU
Wido, Could you tell me the libvirt version? For our platform with this issue, the libvirt version is 0.9.13 -Wei 2013/6/7 Marcus Sorensen > There is already quite a bit of logging around this stuff, for example: > > s_logger.error("deleteStoragePool removed pool from > libvir

Re: Orphaned libvirt storage pools

2013-06-07 Thread Marcus Sorensen
There is already quite a bit of logging around this stuff, for example: s_logger.error("deleteStoragePool removed pool from libvirt, but libvirt had trouble" + "unmounting the pool. Trying umount location " + targetPath

Re: Orphaned libvirt storage pools

2013-06-07 Thread Wido den Hollander
Hi, On 06/07/2013 04:30 PM, Marcus Sorensen wrote: Does this only happen with isos? Yes, it does. My work-around for now was to locate all the Instances who had these ISOs attached and detach them from all (~100 instances..) Then I manually unmounted all the mountpoints under /mnt so that

Re: Orphaned libvirt storage pools

2013-06-07 Thread Marcus Sorensen
I had seen something similar related to the KVM HA monitor (it would re-mount the pools outside of libvirt after they were removed), but anything using getStoragePoolByURI to register a pool shouldn't be added to the KVMHA monitor anymore. That HA monitor script is the only way I know of that cloud

Re: Orphaned libvirt storage pools

2013-06-07 Thread Marcus Sorensen
Does this only happen with isos? On Jun 7, 2013 8:15 AM, "Wido den Hollander" wrote: > Hi, > > So, I just created CLOUDSTACK-2893, but Wei Zhou mentioned that there are > some related issues: > * CLOUDSTACK-2729 > * CLOUDSTACK-2780 > > I restarted my Agent and the issue described in 2893 went awa