I just tried to deploy a fresh 4.1 zone from current 4.1.2, I can't
deploy initial system vms. It immediately takes out a file lock on the
system vm template, and then gets stuck. if I remove the lock, restart
the agent, it immediately goes back into this state:
AGENT (after deleting template/tmpl
Sorry, I think the KVMFILELOCK is left over on secondary storage
because it's unable to lock the primary storage, and doesn't clean up
after itself. I'm not sure why it can't take the lock out on primary
yet... troubleshooting that.
On Wed, Aug 7, 2013 at 4:54 PM, Marcus Sorensen wrote:
> I just
Here's the issue... local storage isn't mounted like remote storage is.
This is invalid for local storage:
String lockFile = _mountPoint + File.separator + pool.getUUIDString()
+ File.separator + _lockfile;
Need to look at storage pool type and change lockfile to path for local storage
On Wed,
Here's the debugging I put in:
2013-08-07 17:39:12,286 DEBUG [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-3:null) attempting to lock pool
2a9c418e-dd56-3f2c-9081-032b877d5644 with file
'/mnt/2a9c418e-dd56-3f2c-9081-032b877d5644/KVMFILELOCK/.lock'
2013-08-07 17:39:12,425 DEBUG [kvm.sto
g
> Subject: Re: [jira] [Commented] (CLOUDSTACK-2729) [Automation] Libvirt
> failed find primary storage and VM deployment failed
>
> Here's the debugging I put in:
>
> 2013-08-07 17:39:12,286 DEBUG [kvm.storage.LibvirtStorageAdaptor]
> (agentRequest-Handler-3:null) att
