cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4443) [VMWARE]Failed to deploy VM's on VMWARE Standard vSwitch Legacy Zone after upgrade
Date Tue, 27 Aug 2013 17:01:56 GMT

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

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

Commit 808183fdcc24fd6417d7bb806ee58a84b84868f4 in branch refs/heads/4.2-forward from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=808183f ]

CLOUDSTACK-4443 [VMWARE]Failed to deploy VM's on VMWARE Standard vSwitch Legacy Zone after
upgrade

While upgrading to 4.2 to support existing clusters working over standard vswitch or nexus
dvswitch should be supported as is. To ensure this while upgrading to 4.2, existing cluster's
vswitch configuration needs to be persisted to database. If zone level traffic label is empty
then default vswitch name would be used.

Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>

                
> [VMWARE]Failed to deploy VM's on VMWARE Standard vSwitch Legacy Zone after upgrade 
> -----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4443
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4443
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade, VMware
>    Affects Versions: 4.2.1
>            Reporter: Sailaja Mada
>            Assignee: Sateesh Chodapuneedi
>            Priority: Blocker
>             Fix For: 4.2.1
>
>         Attachments: deployvmlogs.rar
>
>
> Steps:
> With 307,
> 1. Configure Adv Zone using Standard vSwitch with VMWARE cluster (Single Physical Network
and all the traffics - Mgmt,guest,public) on this default network ( vSwitch0) 
> 2. Upgraded from 307 to 4.2 
> 3. Tried to depoy new VM on this zone which was created in 307. 
> Observation:
> Failed to deploy VM's on VMWARE Standard vSwitch Legacy Zone after upgrade 
> 2013-08-22 12:22:09,336 DEBUG [vmware.resource.VmwareResource] (DirectAgent-50:10.102.192.20)
Prepare volume at new device {"capacityInKB":0,"key":-2,"backing":{"diskMode":"persistent","fileName":"[3adda133ecae3cd894716de45b81a560]
i-4-32-VM/ROOT-32.vmdk","datastore":{"value":"datastore-11157","type":"Datastore"}},"connectable":{"startConnected":true,"allowGuestControl":false,"connected":true},"controllerKey":200,"unitNumber":1}
> 2013-08-22 12:22:09,337 INFO  [vmware.resource.VmwareResource] (DirectAgent-50:10.102.192.20)
Prepare NIC device based on NicTO: {"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"057f0e6e-7ca5-4715-9551-c827f9f61ea8","ip":"10.1.1.74","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:28:84:00:04","dns1":"10.103.128.15","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://782","isolationUri":"vlan://782","isSecurityGroupEnabled":false}
> 2013-08-22 12:22:09,348 INFO  [vmware.resource.VmwareResource] (DirectAgent-50:10.102.192.20)
Prepare network on vmwaresvs P[epp0:untagged] with name prefix: cloud.guest
> 2013-08-22 12:22:09,427 ERROR [vmware.mo.HypervisorHostHelper] (DirectAgent-50:10.102.192.20)
Unable to find vSwitchepp0
> 2013-08-22 12:22:09,444 WARN  [vmware.resource.VmwareResource] (DirectAgent-50:10.102.192.20)
StartCommand failed due to Exception: java.lang.Exception
> Message: Unable to find vSwitchepp0
> java.lang.Exception: Unable to find vSwitchepp0
>         at com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:904)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:3292)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2904)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:514)
>         at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
>         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-22 12:22:09,467 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-50:null)
Seq 7-1913981379: Response Received:
> 2013-08-22 12:22:09,470 DEBUG [agent.transport.Request] (DirectAgent-50:null) Seq 7-1913981379:
Processing:  { Ans: , MgmtId: 187767034175903, via: 7, Ver: v1, Flags: 10, [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":32,"name":"i-4-32-VM","bootloader":"HVM","type":"User","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"hostName":"newinstance1","arch":"x86_64","os":"CentOS
5.3 (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"85cf3117ab67ecba","params":{"rootDiskController":"ide","nicAdapter":"E1000","nestedVirtualizationFlag":"false"},"uuid":"8157294c-b9c6-4589-9727-dffdcf64a8f7","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"8beca59d-c43f-4dc1-8f51-2df6d438286d","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"3adda133-ecae-3cd8-9471-6de45b81a560","id":204,"poolType":"NetworkFilesystem","host":"10.102.192.100","path":"/cpg_vol/sailaja/legacyps1","port":2049}},"name":"ROOT-32","size":2147483648,"path":"ROOT-32","volumeId":86,"vmName":"i-4-32-VM","accountId":4,"format":"OVA","id":86,"hypervisorType":"VMware"}},"diskSeq":0,"type":"ROOT"},{"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,"uuid":"057f0e6e-7ca5-4715-9551-c827f9f61ea8","ip":"10.1.1.74","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:28:84:00:04","dns1":"10.103.128.15","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://782","isolationUri":"vlan://782","isSecurityGroupEnabled":false}]},"result":false,"details":"StartCommand
failed due to Exception: java.lang.Exception\nMessage: Unable to find vSwitchepp0\n","wait":0}}]
}
> 2013-08-22 12:22:09,470 DEBUG [agent.transport.Request] (Job-Executor-9:job-89 = [ 95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd
]) Seq 7-1913981379: Received:  { Ans: , MgmtId: 187767034175903, via: 7, Ver: v1, Flags:
10, { StartAnswer } }
> 2013-08-22 12:22:09,477 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-9:job-89
= [ 95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd ]) Unable to start VM on Host[-7-Routing] due to
StartCommand failed due to Exception: java.lang.Exception
> Message: Unable to find vSwitchepp0
> 2013-08-22 12:22:09,502 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-9:job-89
= [ 95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd ]) Cleaning up resources for the vm VM[User|newinstance1]
in Starting state
> 2013-08-22 12:22:10,023 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-9:job-89 =
[ 95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd ]) No clusters found after removing disabled clusters
and clusters in avoid list, returning.
> 2013-08-22 12:22:10,051 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-9:job-89
= [ 95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd ]) VM state transitted from :Starting to Stopped
with event: OperationFailedvm's original host id: null new host id: null host id before state
transition: null
> 2013-08-22 12:22:10,070 DEBUG [cloud.vm.UserVmManagerImpl] (Job-Executor-9:job-89 = [
95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd ]) Destroying vm VM[User|newinstance1] as it failed to
create on Host with Id:null
> 2013-08-22 12:22:10,098 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-9:job-89
= [ 95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd ]) VM state transitted from :Stopped to Error with
event: OperationFailedToErrorvm's original host id: null new host id: null host id before
state transition: null
> 2013-08-22 12:22:10,169 WARN  [apache.cloudstack.alerts] (Job-Executor-9:job-89 = [ 95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd
])  alertType:: 8 // dataCenterId:: 2 // podId:: 2 // clusterId:: null // message:: Failed
to deploy Vm with Id: 32, on Host with Id: null
> 2013-08-22 12:22:10,288 INFO  [user.vm.DeployVMCmd] (Job-Executor-9:job-89 = [ 95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd
]) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment
for VM[User|newinstance1]Scope=interface com.cloud.dc.DataCenter; id=2
> 2013-08-22 12:22:10,290 INFO  [user.vm.DeployVMCmd] (Job-Executor-9:job-89 = [ 95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd
]) Unable to create a deployment for VM[User|newinstance1]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment
for VM[User|newinstance1]Scope=interface com.cloud.dc.DataCenter; id=2
>         at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:839)
>         at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:575)
>         at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
>         at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
>         at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
>         at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
>         at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
>         at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
>         at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>         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-22 12:22:10,318 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-89
= [ 95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd ]) Complete async job-89 = [ 95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd
], jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable to create a deployment
for VM[User|newinstance1]
> 2013-08-22 12:22:10,517 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null) ===START===
 10.144.6.50 -- GET  command=queryAsyncJobResult&jobId=95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd&response=json&sessionkey=Kf6ovDEJR5oFZHDIYAzrUm8ArR8%3D&_=1377154582972
> 2013-08-22 12:22:10,583 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-17:null)
Async job-89 = [ 95275847-d7bf-43e6-9a8b-8d7fd7f4a2cd ] completed

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