cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajesh Battala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4011) not able to deployVM on kvm due to checking and stopping dom as part of does dom already exists check
Date Sun, 04 Aug 2013 17:15:48 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728919#comment-13728919
] 

Rajesh Battala commented on CLOUDSTACK-4011:
--------------------------------------------

Not able to reproduce it now.
Will verify few more test cases to find out the issue 
                
> not able to deployVM on kvm due to checking and stopping dom as part of does dom already
exists check
> -----------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4011
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4011
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM, Storage Controller
>    Affects Versions: 4.2.0
>         Environment: KVM, advance zone
> ZWPS
>            Reporter: Rajesh Battala
>            Assignee: Rajesh Battala
>            Priority: Blocker
>             Fix For: 4.2.0
>
>
> While deploying the instance in KVM,
> its checking whether the dom is already present or not by searching the dom and trying
to stop it. 
> As the dom is not present, its throwing the below exception and deploy is failing. 
> I guess it good to check if the dom is present by lookup and continue further instead
of stopping a dom which is not present which will definitely throw an exception and deploy
fails
> 2013-08-01 17:34:32,819 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null) Processing
command: com.cloud.agent.api.StopCommand
> 2013-08-01 17:34:32,822 DEBUG [kvm.resource.LibvirtConnection] (agentRequest-Handler-1:null)
can't find connection: KVM, for vm: i-2-9-VM, continue
> 2013-08-01 17:34:32,825 DEBUG [kvm.resource.LibvirtConnection] (agentRequest-Handler-1:null)
can't find connection: LXC, for vm: i-2-9-VM, continue
> 2013-08-01 17:34:32,825 DEBUG [kvm.resource.LibvirtConnection] (agentRequest-Handler-1:null)
can't find which hypervisor the vm used , then use the default hypervisor
> 2013-08-01 17:34:32,828 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
Failed to get dom xml: org.libvirt.LibvirtException: Domain not found: no domain with matching
name 'i-2-9-VM'
> 2013-08-01 17:34:32,830 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
Failed to get dom xml: org.libvirt.LibvirtException: Domain not found: no domain with matching
name 'i-2-9-VM'
> 2013-08-01 17:34:32,832 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
Failed to get dom xml: org.libvirt.LibvirtException: Domain not found: no domain with matching
name 'i-2-9-VM'
> 2013-08-01 17:34:32,832 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py destroy_network_rules_for_vm
--vmname i-2-9-VM
> 2013-08-01 17:34:33,042 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
Execution is successful.
> 2013-08-01 17:34:33,043 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
Try to stop the vm at first
> 2013-08-01 17:34:33,046 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
Failed to stop VM :i-2-9-VM :
> org.libvirt.LibvirtException: Domain not found: no domain with matching name 'i-2-9-VM'
>         at org.libvirt.ErrorHandler.processError(Unknown Source)
>         at org.libvirt.Connect.processError(Unknown Source)
>         at org.libvirt.Connect.domainLookupByName(Unknown Source)
>         at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.stopVM(LibvirtComputingResource.java:4207)
>         at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.stopVM(LibvirtComputingResource.java:4159)
>         at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3036)
>         at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1152)
>         at com.cloud.agent.Agent.processRequest(Agent.java:525)
>         at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
>         at com.cloud.utils.nio.Task.run(Task.java:83)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-08-01 17:34:33,048 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
Failed to get vm status:Domain not found: no domain with matching name 'i-2-9-VM'
> 2013-08-01 17:34:33,050 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
Failed to get vm status:Domain not found: no domain with matching name 'i-2-9-VM'
> 2013-08-01 17:34:33,052 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
Failed to get vm status:Domain not found: no domain with matching name 'i-2-9-VM'
> 2013-08-01 17:34:33,052 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
Can't get vm's status, assume it's dead already

--
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

Mime
View raw message