[
https://issues.apache.org/jira/browse/CLOUDSTACK-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642749#comment-13642749
]
Sateesh Chodapuneedi commented on CLOUDSTACK-2171:
--------------------------------------------------
Kiran,
Unable to reproduce the issue with the provided steps.
As mentioned earlier the difference with the setup, where this issue is
observed, is that invocation of UpdateTrafficTypeCmd. Wondering what step
caused the following log message, this is not part of deployVM command.
2013-04-24 21:53:00,403 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-22:null) submit async job-13, details: AsyncJobVO {id:13,
userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId:
null, cmd: org.apache.cloudstack.api.command.admin.usage.UpdateTrafficTypeCmd,
cmdOriginator: null, cmdInfo:
{"sessionkey":"+m6qLsvPI+P0D69KEOxalRy237c\u003d","ovmnetworklabel":"undefined","ctxUserId":"2","xennetworklabel":"undefined","httpmethod":"GET","kvmnetworklabel":"undefined","id":"b40b7dc3-6372-45bb-981b-4c450b7b637d","response":"json","_":"1366801013937","vmwarenetworklabel":"undefined","ctxAccountId":"2","lxcnetworklabel":"undefined","ctxStartEventId":"52"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
Please let me know if you tried to update physical network traffic labels.
> Unable to Create a VM In the VMware Setup with the latest Master.
> -----------------------------------------------------------------
>
> Key: CLOUDSTACK-2171
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2171
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
> Affects Versions: 4.2.0
> Reporter: Kiran Koneti
> Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> I have created a VMware Advanced Zone Setup.
> Once the system Vm's came up I added a template and tried to create a VM for
> the first time.
> The Router VM is created and the VM also came up.
> Then I tried to create another VM this the the VM fails with an error message
> saying insufficient capacity.
> When started debugging the issue I found that the VM creation initially
> failed with an error message as below.
> "c":true,"uuid":"9c0b7d10-be63-4bd3-8e07-9e3e86955fd6","ip":"10.1.1.2","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:49:1b:00:05","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://923","isolationUri":"vlan://923","isSecurityGroupEnabled":false,"name":"undefined"}
> 2013-04-24 22:14:22,636 INFO [vmware.resource.VmwareResource]
> (DirectAgent-66:10.147.40.9) Prepare network on vmwaresvs
> P[undefined:untagged] with name prefix: cloud.guest
> 2013-04-24 22:14:22,660 ERROR [vmware.mo.HypervisorHostHelper]
> (DirectAgent-66:10.147.40.9) Unable to find vSwitchundefined
> 2013-04-24 22:14:22,660 WARN [vmware.resource.VmwareResource]
> (DirectAgent-66:10.147.40.9) StartCommand failed due to Exception:
> java.lang.Exception
> Message: Unable to find vSwitchundefined
> java.lang.Exception: Unable to find vSwitchundefined
> at
> com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:697)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2532)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2308)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:433)
> 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)"
> When started debugging the issue there is a new field added to the VM start
> command with as "name":"undefined" after the "isSecurityGroupEnabled":false
> which I didn't observe for the VM created for the first time.
> The Start command for the VM which was created Successfully is as below:
> "2013-04-24 21:51:55,245 INFO [vmware.resource.VmwareResource]
> (DirectAgent-17:10.147.40.9) Executing resource StartCommand:
> {"vm":{"id":3,"name":"i-2-3-VM","bootloader":"HVM","type":"User","cpus":1,"minSpeed":1000,"maxSpeed":1000,"minRam":1073741824,"maxRam":1073741824,"arch":"x86_64","os":"CentOS
> 5.3
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"67afc54d34162749","params":{"rootDiskController":"ide","nicAdapter":"E1000","nestedVirtualizationFlag":"false"},"uuid":"876c4e5b-0549-40a5-9ac6-07ee6b94bab7","disks":[{"id":3,"name":"ROOT-3","mountPoint":"/export/home/kiran/p1","path":"ROOT-3-3","size":2147483648,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"b4825bd6-2b6d-33ef-b324-bfbbec982716","deviceId":0},{"id":4,"name":"DATA-3","mountPoint":"/export/home/kiran/p1","path":"604556bb425a4368853736a5731c262a","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"b4825bd6-2b6d-33ef-b324-bfbbec982716","deviceId":1},{"id":3,"name":"Cent5.3","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"693265ac-6324-4dab-96d1-2d2142010eb1","ip":"10.1.1.203","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:11:cb:00:01","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://923","isolationUri":"vlan://923","isSecurityGroupEnabled":false}]},"hostIp":"10.147.40.9","wait":0}"
> The Start command executed when the VM creation failed is as below:
> "2013-04-24 22:14:20,876 INFO [vmware.resource.VmwareResource]
> (DirectAgent-66:10.147.40.9) Executing resource StartCommand:
> {"vm":{"id":7,"name":"i-2-7-VM","bootloader":"HVM","type":"User","cpus":1,"minSpeed":1000,"maxSpeed":1000,"minRam":1073741824,"maxRam":1073741824,"arch":"x86_64","os":"CentOS
> 5.3
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"50dea6f1e13fec97","params":{"rootDiskController":"ide","nicAdapter":"E1000","nestedVirtualizationFlag":"false"},"uuid":"875433b8-8673-4307-9e1e-8cb3e133b8c1","disks":[{"id":9,"name":"ROOT-7","mountPoint":"/export/home/kiran/p1","path":"ROOT-7-9","size":2147483648,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"b4825bd6-2b6d-33ef-b324-bfbbec982716","deviceId":0},{"id":7,"name":"Cent5.3","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"9c0b7d10-be63-4bd3-8e07-9e3e86955fd6","ip":"10.1.1.2","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:49:1b:00:05","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://923","isolationUri":"vlan://923","isSecurityGroupEnabled":false,"name":"undefined"}]},"hostIp":"10.147.40.9","wait":0}"
> Attaching the management server logs for the further verification.
--
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
