You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/09/04 17:35:52 UTC

[jira] [Commented] (CLOUDSTACK-7473) [LXC]putting host into maintenance is failing

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

ASF subversion and git services commented on CLOUDSTACK-7473:
-------------------------------------------------------------

Commit 6f7c4863a2e40b05a3bd43f992bd114bae485462 in cloudstack's branch refs/heads/master from [~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6f7c486 ]

CLOUDSTACK-7473: Vm migration is not supported for LXC. When host is put in maintenance mode, stop the Vms instead of migrating


> [LXC]putting host into maintenance is failing 
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-7473
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7473
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.5.0
>            Reporter: shweta agarwal
>            Assignee: Kishan Kavala
>            Priority: Blocker
>         Attachments: agent.log.tar.gz, ms.tar.gz
>
>
> Repro stesp:
> 1. create a zone with a LXC cluster having 2 host
> 2. create few LXC vms
> 3. Put one host into maintenance which has some VM  running
> Bug:
> Putting host into maintenance will never pass. host will remain in preparing for maintenance stage and then goes to disconnect state.
> Agent log shows :
> 2014-09-02 19:08:12,663 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null) Failed to execute while migrating domain: org.libvirt.LibvirtException: this function is not supported by the connection driver: virDomainMigrate2
> 2014-09-02 19:08:12,665 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null) Seq 1-3693233169420517550:  { Ans: , MgmtId: 233845178472723, via: 1, Ver: v1, Flags: 10, [{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException: this function is not supported by the connection driver: virDomainMigrate2","wait":0}}] }
> 2014-09-02 19:08:13,004 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:null) Request:Seq 1-3693233169420517551:  { Cmd , MgmtId: 233845178472723, via: 1, Ver: v1, Flags: 100011, [{"com.cloud.agent.api.MigrateCommand":{"vmName":"i-2-7-VM","destIp":"10.147.28.49","hostGuid":"2b2a1b9f-7582-378f-b54f-1dbb8f69e239-LibvirtComputingResource","isWindows":false,"vmTO":{"id":7,"name":"i-2-7-VM","type":"User","cpus":1,"minSpeed":128,"maxSpeed":128,"minRam":134217728,"maxRam":134217728,"arch":"x86_64","os":"Red Hat Enterprise Linux 7.0","platformEmulator":"Other","bootArgs":"","enableHA":true,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"QY0cKnTfogzaS49R283f1g==","params":{"Message.ReservedCapacityFreed.Flag":"false"},"uuid":"caf07a92-9f6c-49df-a7e4-27289e715448","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"981fe152-6ee5-4444-ae41-474736c881cf","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"dfa2ec3c-d133-3284-8583-0a0845aa4424","id":1,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/shweta/goleta.lxc.primary","port":2049,"url":"NetworkFilesystem://10.147.28.7/export/home/shweta/goleta.lxc.primary/?ROLE=Primary&STOREUUID=dfa2ec3c-d133-3284-8583-0a0845aa4424"}},"name":"ROOT-7","size":647321600,"path":"981fe152-6ee5-4444-ae41-474736c881cf","volumeId":7,"vmName":"i-2-7-VM","accountId":2,"format":"DIR","provisioningType":"THIN","id":7,"deviceId":0,"hypervisorType":"LXC"}},"diskSeq":0,"path":"981fe152-6ee5-4444-ae41-474736c881cf","type":"ROOT","_details":{"managed":"false","storagePort":"2049","storageHost":"10.147.28.7","volumeSize":"647321600"}},{"data":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":0,"format":"ISO","accountId":0,"hvm":false}},"diskSeq":3,"type":"ISO"}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"pxeDisable":false,"nicUuid":"95826449-4163-46b8-91b7-8bf94f19ab8e","uuid":"d4db3da8-4e6c-4e29-b6bb-a6613d55fa2f","ip":"10.147.30.166","netmask":"255.255.255.0","gateway":"10.147.30.1","mac":"06:54:96:00:00:07","dns1":"10.140.50.6","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://30","isolationUri":"vlan://30","isSecurityGroupEnabled":true}]},"executeInSequence":false,"wait":0}}] }
> 2014-09-02 19:08:13,005 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:null) Processing command: com.cloud.agent.api.MigrateCommand
> 2014-09-02 19:08:13,006 DEBUG [kvm.resource.LibvirtConnection] (agentRequest-Handler-4:null) can't find connection: KVM, for vm: i-2-7-VM, continue
> 2014-09-02 19:08:13,018 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null) Live migration of instance i-2-7-VM initiated
> 2014-09-02 19:08:13,103 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-5:null) Waiting for migration of s-1-VM to complete, waited 1000ms
> 2014-09-02 19:08:13,118 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null) Migration thread for i-2-7-VM is done
> 2014-09-02 19:08:13,119 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null) Failed to execute while migrating domain: org.libvirt.LibvirtException: this function is not supported by the connection driver: virDomainMigrate2
> 2014-09-02 19:08:13,124 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:null) Seq 1-3693233169420517551:  { Ans: , MgmtId: 233845178472723, via: 1, Ver: v1, Flags: 10, [{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException: this function is not supported by the connection driver: virDomainMigrate2","wait":0}}] }
> 2014-09-02 19:08:13,158 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Waiting for migration of r-4-VM to complete, waited 1000ms
> 2014-09-02 19:08:13,234 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) Waiting for migration of v-2-VM to complete, waited 1000ms
> 2014-09-02 19:08:14,104 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-5:null) Waiting for migration of s-1-VM to complete, waited 2000ms
> 2014-09-02 19:08:14,159 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Waiting for migration of r-4-VM to complete, waited 2000ms
> 2014-09-02 19:08:14,235 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) Waiting for migration of v-2-VM to complete, waited 2000ms
> 2014-09-02 19:08:15,105 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-5:null) Waiting for migration of s-1-VM to complete, waited 3000ms
> 2014-09-02 19:08:15,159 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Waiting for migration of r-4-VM to complete, waited 3000ms
> 2014-09-02 19:08:15,235 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) Waiting for migration of v-2-VM to complete, waited 3000ms
> 2014-09-02 19:08:16,106 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-5:null) Waiting for migration of s-1-VM to complete, waited 4000ms
> 2014-09-02 19:08:16,160 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Waiting for migration of r-4-VM to complete, waited 4000ms
> 2014-09-02 19:08:16,236 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) Waiting for migration of v-2-VM to complete, waited 4000ms
> 2014-09-02 19:08:16,761 INFO  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Migration thread for r-4-VM is done
> 2014-09-02 19:08:16,763 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Failed to get dom xml: org.libvirt.LibvirtException: Domain not found: no domain with matching name 'r-4-VM'
> @
>                                                                                                            
> Attaching MS logs and agent logs for the same                            



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)