Re: [jira] [Updated] (CLOUDSTACK-2893) The Agent attempts to re-create a already existing Libvirt Storage pool when creating a volume

[Marcus Sorensen <sh...@gmail.com>]

I did see this once, normally the agent keeps a map of which pools are
installed. I believe it was triggered by putting the host into maintenance
and then reconnecting without stopping the agent. Restarting the agent
fixed the problem without further intervention, the agent discovered the
existing pools as expected.

Otherwise, the volume commands can and should try to recreate the pool if
it is not really there.
On Jun 7, 2013 6:43 AM, "Wido den Hollander (JIRA)" <ji...@apache.org> wrote:

>
>      [
> https://issues.apache.org/jira/browse/CLOUDSTACK-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Wido den Hollander updated CLOUDSTACK-2893:
> -------------------------------------------
>
>     Assignee: Wido den Hollander
>
> > The Agent attempts to re-create a already existing Libvirt Storage pool
> when creating a volume
> >
> ----------------------------------------------------------------------------------------------
> >
> >                 Key: CLOUDSTACK-2893
> >                 URL:
> https://issues.apache.org/jira/browse/CLOUDSTACK-2893
> >             Project: CloudStack
> >          Issue Type: Bug
> >      Security Level: Public(Anyone can view this level - this is the
> default.)
> >          Components: KVM
> >    Affects Versions: 4.1.0
> >         Environment: - Ubuntu 12.04.2
> > - Libvirt 1.0.2 (Cloud Archive PPA from Canonical)
> > - CloudStack 4.1
> >            Reporter: Wido den Hollander
> >            Assignee: Wido den Hollander
> >             Fix For: 4.1.1
> >
> >
> > When trying to deploy a new Instance I saw the following Exception in my
> logs:
> > 2013-06-07 08:19:18,832 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-7:null) Processing command:
> com.cloud.agent.api.storage.CreateCommand
> > 2013-06-07 08:19:18,840 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-7:null) Failed to create volume:
> com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: Requested operation is not valid: Target
> '/mnt/52801816-fe44-3a2b-a147-bb768eeea295' is already mounted
> > 2013-06-07 08:19:18,841 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-7:null) Seq 12-477959384:  { Ans: , MgmtId:
> 207376724852, via: 12, Ver: v1, Flags: 110,
> [{"storage.CreateAnswer":{"requestTemplateReload":false,"result":false,"details":"Exception:
> com.cloud.utils.exception.CloudRuntimeException\nMessage:
> org.libvirt.LibvirtException: Requested operation is not valid: Target
> '/mnt/52801816-fe44-3a2b-a147-bb768eeea295' is already mounted\nStack:
> com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: Requested operation is not valid: Target
> '/mnt/52801816-fe44-3a2b-a147-bb768eeea295' is already mounted\n\tat
> com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getStoragePool(LibvirtStorageAdaptor.java:427)\n\t
> > at
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.getStoragePool(KVMStoragePoolManager.java:71)\n\t
> > at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:1271)\n\t
> > at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1072)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:525)\n\t
> > at
> com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat
> com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
> java.lang.Thread.run(Thread.java:679)\n","wait":0}}] }
> > The Agent seems to try and create the storage pool again and Libvirt
> will try to mount it, but it is already mounted.
> > The Storage pool is actually already running on that Hypervisor, but
> there seems to be a miscommuncation between libvirt and the Agent.
>
> --
> 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
>