Short update for anyone (besides Mike) interested in this thread: the VMware has different naming (strings) used for controller names if they are in VMX (VMware specific) or in OVA (vendor-neutral) - so Mike was hitting/using templates/appliances which had only last 2, unsupported by 4.15.0, controllers - bad luck :)
But it's being fixed in 4.15.1 (RC2) Details for nerds: vCenter UI VMX OVF BusLogic Parallel NA (not specified!) buslogic LSI Logic Parallel lsilogic lsilogic LSI Logic SAS **lsisas1068** **lsilogicsas** VMware Paravirtual **pvscsi** **VirtualSCSI** The last 2 are different in OVF (generic OVF terminology) vs. what they are inside VMX (specific on how VMware implements it) Best, On Wed, 2 Jun 2021 at 19:31, Andrija Panic <[email protected]> wrote: > Yes, that should all be specified in OVF, so it's hiden from template > registration form. > > On Wed, 2 Jun 2021, 18:04 Corey, Mike, <[email protected]> wrote: > >> One area of change, not sure if it matters in my case, is that I can no >> longer specify the BIOS or EFI option of the instance/template. >> >> In the old UI, when deploying an instance I could select the bios/efi in >> the same window as controller and keyboard language etc. This option is >> NOT an option in the new UI under the template settings pane. >> >> >> >> >> >> >> -----Original Message----- >> From: Corey, Mike >> Sent: Wednesday, June 2, 2021 9:28 AM >> To: [email protected] >> Subject: RE: VMware Instance Error >> >> I saw that too - but that line regarding format is "ISO" for other >> deployments. >> >> Example - I used an Ubuntu OVA from openvm and it deployed with the same >> message... >> >> >> {"org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":"0","format":"ISO","accountId":"0","hvm":"false","bootable":"false","directDownload":"false","deployAsIs":"false"}},"diskSeq":"3","type":"ISO"}],"nics":[{"deviceId":"0","networkRateMbps":"200","defaultNic":"true" >> >> Mike >> >> -----Original Message----- >> From: Abhishek Kumar <[email protected]> >> Sent: Tuesday, June 1, 2021 4:18 PM >> To: [email protected] >> Subject: Re: VMware Instance Error >> >> Hi Mike, >> >> For your deployment/disk controller error, you should check the template >> you are using for the VM. From the logs you have shared there is something >> wrong with the StartCommand. >> >> --- >> >> org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":"0","format":"ISO","accountId":"0","hvm":"false","bootable":"false" >> --- >> Not sure why id is 0 there and the format is ISO. Are you using an ISO to >> deploy the VM? >> >> Regards, >> Abhishek >> ________________________________ >> From: Andrija Panic <[email protected]> >> Sent: 02 June 2021 01:38 >> To: users <[email protected]> >> Subject: Re: VMware Instance Error >> >> Mike, >> >> are you in a position to share that specific template (if licencing >> allows, >> if it's trial, etc) - ping me on email directly - and I can give it a spin >> in the lab on 4.15 >> 4.15.1 should bring this new VMware template behaviour (read from OVF, >> instead of allowing you to specify OS, NIC/disk controllers, etc) - AS >> OPTIONAL - so you can wait for 4.15.1 if you use non-standard OVA >> appliances (or, for that matter, the ones that simply don't work with ACS, >> for whatever reasons) >> >> Best, >> >> >> >> >> On Tue, 1 Jun 2021 at 21:46, Corey, Mike <[email protected]> >> wrote: >> >> > Another development in my troubleshooting this... >> > >> > I used a vendor (OEM) supplied ova appliance as a template and >> downloaded >> > in the same manner. NO SETTINGS were created for the template by ACS. >> > >> > If the expected behavior is for ACS to add settings based off of the OVF >> > descriptor - my case IS NOT. >> > >> > I could really use some guidance here on troubleshooting as to why the >> > template settings are NOT being created by ACS. >> > >> > Again - anyone running ACS 4.15 with VMware and having success with >> using >> > templates? >> > >> > Any other logs I can check to determine why ACS is not creating these >> > custom setting attributes on the templates? >> > >> > Many thanks! >> > >> > Mike >> > >> > -----Original Message----- >> > From: Corey, Mike <[email protected]> >> > Sent: Tuesday, June 1, 2021 8:47 AM >> > To: [email protected] >> > Subject: [CAUTION] RE: VMware Instance Error >> > >> > Thanks for the reply Abhishek! >> > >> > 1- ACS deploys the VM from template; however, it fails and shows Error >> in >> > ACS-Instances UI. So the VM remains in vCenter - that VM has the >> CPU/RAM >> > as the template NOT what the ACS service offering (Small Instance) I >> > selected. I suppose ACS is not finishing the configuration because the >> > deployment fails. >> > >> > 3 - This is the issue I need help to troubleshoot. ACS IS NOT creating >> > any settings on the Windows 10 and CentOS template I've uploaded into >> ACS. >> > Both template OVF files have the hardware descriptions used by the >> template >> > VM. However, NO SETTINGS are being added to the ACS template. >> > >> > How can this be troubleshot? Obviously, ACS is NOT populating the >> > settings on the template as expected - what could be the issue? What >> > commands occur when the template is downloaded and populate the >> settings of >> > the template (so I can search for errors)? Is something supposed to be >> > written to ACS but is not due to permissions or file doesn't exist? >> > >> > Item 1 & 4 - Yes, the VM in vCenter is named the same as the ones that >> > fail deployment in ACS (i-2-##-vm) - the VM has resources of the >> template >> > (not service offering) and powers ON and loads OS. >> > >> > 5 - snippet from logs below - diskcontroller is being identified by OVF >> - >> > nothing is set by ACS on template. >> > >> > INFO [c.c.h.v.r.VmwareResource] (DirectAgent-496:ctx-f077199e >> > usphlmvesxt01.phl.global.corp.sap, job-164/job-166, cmd: StartCommand) >> > (logid:6c707559) Executing resource StartCommand: >> > >> {"vm":{"id":"26","name":"i-2-26-VM","bootloader":"HVM","state":"Starting","type":"User","cpus":"1","minSpeed":"166","maxSpeed":"500","minRam":"(512.00 >> > MB) 536870912","maxRam":"(512.00 MB) >> > 536870912","hostName":"June1-01","arch":"x86_64","os":"Windows 10 >> > >> (64-bit)","platformEmulator":"windows9_64Guest","bootArgs":"","enableHA":"false","limitCpuUse":"false","enableDynamicallyScaleVm":"false","vncPassword":"X1k9AVje8WIPzXb_8P_88Q","params":{"deployvm":"true","dataDiskController":"scsi","memoryOvercommitRatio":"1.0","Message.ReservedCapacityFreed.Flag":"false","nestedVirtualizationFlag":"false","cpuOvercommitRatio":"3.0","vmware.reserve.mem":"false","vmware.reserve.cpu":"false","nicAdapter":"E1000","rootDiskController":"lsilogicsas"},"uuid":"dafd18a5-04a9-4bda-b701-0d24e4b1e61d","enterHardwareSetup":"false","disks":[{"data":{"org.apache. >> > cloudstack.storage.to >> > >> .VolumeObjectTO":{"uuid":"973a1795-4569-4769-afcb-93e3911be12e","volumeType":"ROOT","dataStore":{"org. >> > apache.cloudstack.storage.to >> .PrimaryDataStoreTO":{"uuid":"9df43ec0-1e52-3cc3-8e5a-bf2313bbbd8d","id":"1","poolType":"NetworkFilesystem","host":"usphlcv302.phl.global.corp.sap","path":"/usphlmvesx_lab_cspri01","port":"2049","url":"NetworkFilesystem://####/usphlmvesx_lab_cspri01/?ROLE=Primary&STOREUUID=9df43ec0-1e52-3cc3-8e5a-bf2313bbbd8d","isManaged":"false"}},"name":"ROOT-26-0","size":"(80.00 >> > GB) >> > >> 85899345920","volumeId":"17","vmName":"i-2-26-VM","accountId":"2","format":"OVA","provisioningType":"THIN","id":"17","deviceId":"0","bytesReadRate":"(0 >> > bytes) 0","bytesWriteRate":"(0 bytes) 0","iopsReadRate":"(0 bytes) >> > 0","iopsWriteRate":"(0 bytes) >> > >> 0","hypervisorType":"VMware","directDownload":"false","deployAsIs":"true"}},"diskSeq":"0","type":"ROOT","_details":{"storageHost":"usphlcv302.phl.global.corp.sap","managed":"false","storagePort":"2049","volumeSize":"(80.00 >> > GB) 85899345920"}},{"data":{"org.apache.cloudstack.storage.to >> .TemplateObjectTO":{"id":"0","format":"ISO","accountId":"0","hvm":"false","bootable":"false","directDownload":"false","deployAsIs":"false"}},"diskSeq":"3","type":"ISO"}],"nics":[{"deviceId":"0","networkRateMbps":"200","defaultNic":"true","pxeDisable":"false","nicUuid":"7587229e-bbb3-4e65-b093-fa9ff690bb43","details":{"MacAddressChanges":"true","ForgedTransmits":"true","PromiscuousMode":"false"},"dpdkEnabled":"false","uuid":"62bfbed1-d07c-4886-b4f4-bf594543bb28","ip":"10.4.80.238","netmask":"255.255.240.0","gateway":"10.4.80.1","mac":"1e:00:9d:00:00:4d","dns1":,"dns2":"","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan:// >> > ","isolationUri":"vlan:// >> > >> ","isSecurityGroupEnabled":"false","name":"vds3-phl-csm02-vm,138,vmwaredvs"}],"guestOsDetails":{},"extraConfig":{},"deployAsIsInfo":{"nicAdapterMap":{}}},"hostIp":"","executeInSequence":"true","wait":"0"} >> > 2021-06-01 08:12:41,346 WARN [c.c.a.m.DirectAgentAttache] >> > (DirectAgent-496:ctx-f077199e) (logid:6c707559) Seq >> 1-7962082666214335044: >> > Throwable caught while executing command >> > com.cloud.utils.exception.CloudRuntimeException: Invalid root disk >> > controller detected : none >> > >> > Many thanks! >> > >> > Mike >> > >> > >> > -----Original Message----- >> > From: Abhishek Kumar <[email protected]> >> > Sent: Monday, May 31, 2021 8:46 AM >> > To: [email protected] >> > Subject: Re: VMware Instance Error >> > >> > Hi Mike, >> > >> > 1 - The CPU/RAM and network on the VMware side should match the >> selected >> > config from ACS end. Make sure you are checking the same ACS and vCenter >> > VM. You may match the internal name. >> > 2 - Mentioned logs are DEBUG logs. Wrt deployment behaviour, ACS first >> > tries to allocate from reserved capacity and if that is not possible >> then >> > from free capacity. So these logs are certainly not the reason for your >> > deployment failure. >> > 3 - Yes, for VMware, in 4.15.0, settings are populated from OVF. >> > rootDiskController, dataDiskController and nicAdapter if found are >> shown in >> > the settings tab in UI. Other details are returned as deployasisdetails >> > parameter in the listTemplates API response. >> > 4 - Again make sure it is the same VM in ACS and VMware. You may check >> for >> > exact error in the management server logs for deployment or VM start >> > failure. >> > 5 - "com.cloud.utils.exception.CloudRuntimeException: Invalid root disk >> > controller detected : none" error is returned by ACS's VMware plugin. >> > Please check the rootDiskController value in StartCommand of the VM in >> > management logs. Valid values are here - >> > >> https://github.com/apache/cloudstack/blob/4.15.0.0/vmware-base/src/main/java/com/cloud/hypervisor/vmware/mo/DiskControllerType.java#L20-L26 >> > >> > Log messages such as "Unable to find matched VM in CloudStack DB. name: >> > ffe8ca8a-4c58-4c47-b93d-c524f90453cf" are due to the fact that vmware >> sdk >> > used returns templates registered in the vCenter as VM in the API >> response. >> > Since these cannot be found in the vm_instance table of ACS it logs them >> > with this message in DEBUG. >> > >> > Hope this helps. >> > >> > Regards, >> > Abhishek >> > >> > ________________________________ >> > From: Corey, Mike <[email protected]> >> > Sent: 28 May 2021 20:36 >> > To: [email protected] <[email protected]> >> > Subject: RE: VMware Instance Error >> > >> > I'll update this email distro in parallel to my ShapeBlue GURU ticket... >> > >> > I continue to have trouble deploying VMs from template. A few more >> > observations to hopefully bring light to the problem. >> > >> > 1 - The VM instance in vCenter shows as having the same CPU/RAM as the >> > template - NOT what the service offering selected. Shouldn't the VM >> > instance be built with the specs of the service offering? It also is >> not >> > being provisioned a NIC (template does not include nic). >> > >> > 2 - I have entries regarding host capacity not being enough, even though >> > these are BEEFY @ 96cores and 750GB RAM... >> > 2021-05-28 09:00:45,987 DEBUG [c.c.c.CapacityManagerImpl] >> > (Work-Job-Executor-4:ctx-338f46d9 job-135/job-137 ctx-312869ec) >> > (logid:8bef4350) Host does not have enough reserved CPU available, >> cannot >> > allocate to this host. >> > 2021-05-28 09:00:45,987 DEBUG [c.c.c.CapacityManagerImpl] >> > (Work-Job-Executor-4:ctx-338f46d9 job-135/job-137 ctx-312869ec) >> > (logid:8bef4350) Checking if host: 2 has enough capacity for requested >> CPU: >> > 1000 and requested RAM: (1.00 GB) 1073741824 , >> cpuOverprovisioningFactor: >> > 3.0 >> > 2021-05-28 09:00:45,988 DEBUG [c.c.c.CapacityManagerImpl] >> > (Work-Job-Executor-4:ctx-338f46d9 job-135/job-137 ctx-312869ec) >> > (logid:8bef4350) Hosts's actual total CPU: 229824 and CPU after applying >> > overprovisioning: 689472 >> > >> > 3 - I've been told that template settings (VMware specifically) should >> be >> > populated by ACS during the upload of a template. This is not the case >> for >> > me - either Win10 or CentOS templates. Could someone answer what is the >> > expected behavior during the install of a template? >> > >> > 4 - Even though ACS says the VM instance is in ERROR status - the VM in >> > vCenter powers on and starts into Windows. >> > >> > 5- Invalid root disk error: even though global setting is set to scsi. >> NO >> > settings are on the template though because they aren't being populated >> > during template installation (item 3) >> > 2021-05-28 09:00:44,442 WARN [c.c.a.m.DirectAgentAttache] >> > (DirectAgent-29:ctx-70d83f01) (logid:8bef4350) Seq >> 1-6066630173044768803: >> > Throwable caught while executing command >> > com.cloud.utils.exception.CloudRuntimeException: Invalid root disk >> > controller detected : none >> > >> > 2021-05-28 09:00:44,443 DEBUG [c.c.a.t.Request] >> > (DirectAgent-29:ctx-70d83f01) (logid:8bef4350) Seq >> 1-6066630173044768803: >> > Processing: { Ans: , MgmtId: 345050012965, via: 1(host), Ver: v1, >> Flags: >> > 110, >> > >> [{"com.cloud.agent.api.Answer":{"result":"false","details":"com.cloud.utils.exception.CloudRuntimeException: >> > Invalid root disk controller detected : none","wait":"0"}}] } >> > >> > 2021-05-28 09:00:44,520 DEBUG [c.c.v.VmWorkJobHandlerProxy] >> > (Work-Job-Executor-3:ctx-1aea8c24 job-135/job-136 ctx-f15549a6) >> > (logid:8bef4350) Done executing VM work job: >> > >> com.cloud.vm.VmWorkStart{"dcId":1,"podId":1,"clusterId":1,"hostId":1,"rawParams":{"VmPassword":"rO0ABXQADnNhdmVkX3Bhc3N3b3Jk"},"userId":2,"accountId":2,"vmId":22,"handlerName":"VirtualMachineManagerImpl"} >> > 2021-05-28 09:00:44,521 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] >> > (Work-Job-Executor-3:ctx-1aea8c24 job-135/job-136 ctx-f15549a6) >> > (logid:8bef4350) Complete async job-136, jobStatus: FAILED, resultCode: >> 0, >> > result: >> > >> rO0ABXNyAC9jb20uY2xvdWQudXRpbHMuZXhjZXB0aW9uLkNsb3VkUnVudGltZUV4Y2VwdGlvbgAAAABWTU9yAwABSQALY3NFcnJvckNvZGV4cgAaamF2YS5sYW5nLlJ1bnRpbWVFeGNlcHRpb26eXwZHCjSD5QIAAHhyABNqYXZhLmxhbmcuRXhjZXB0aW9u0P0fPho7HMQCAAB4cgATamF2YS5sYW5nLlRocm93YWJsZdXGNSc5d7jLAwAETAAFY2F1c2V0ABVMamF2YS9sYW5nL1Rocm93YWJsZTtMAA1kZXRhaWxNZXNzYWdldAASTGphdmEvbGFuZy9TdHJpbmc7WwAKc3RhY2tUcmFjZXQAHltMamF2YS9sYW5nL1N0YWNrVHJhY2VFbGVtZW50O0wAFHN1cHByZXNzZWRFeGNlcHRpb25zdAAQTGphdmEvdXRpbC9MaXN0O3hwcQB-AAh0ABtVbmFibGUgdG8gc3RhcnQgVk0gaW5zdGFuY2V1cgAeW0xqYXZhLmxhbmcuU3RhY2tUcmFjZUVsZW1lbnQ7AkYqPDz9IjkCAAB4cAAAABRzcgAbamF2YS5sYW5nLlN0YWNrVHJhY2VFbGVtZW50YQnFmiY23YUCAAhCAAZmb3JtYXRJAApsaW5lTnVtYmVyTAAPY2xhc3NMb2FkZXJOYW1lcQB-AAVMAA5kZWNsYXJpbmdDbGFzc3EAfgAFTAAIZmlsZU5hbWVxAH4ABUwACm1ldGhvZE5hbWVxAH4ABUwACm1vZHVsZU5hbWVxAH4ABUwADW1vZHVsZVZlcnNpb25xAH4ABXhwAQAAFV10AANhcHB0ACZjb20uY2xvdWQudm0uVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbHQAHlZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwuamF2YXQAEG9yY2hlc3RyYXRlU3RhcnRwcHNxAH4ADAL____-cHQALWpkay5pbnRlcm5hbC5yZWZsZWN0Lk5hdGl2ZU1ldGhvZEFjY2Vzc29ySW1wbHQAHU5hdGl2ZU1ldGhvZEFjY2Vzc29ySW1wbC5qYXZhdAAHaW52b2tlMHQACWphdmEuYmFzZXQABzExLjAuMTFzcQB-AAwCAAAAPnBxAH4AE3EAfgAUdAAGaW52b2tlcQB-ABZxAH4AF3NxAH4ADAIAAAArcHQAMWpkay5pbnRlcm5hbC5yZWZsZWN0LkRlbGVnYXRpbmdNZXRob2RBY2Nlc3NvckltcGx0ACFEZWxlZ2F0aW5nTWV0aG9kQWNjZXNzb3JJbXBsLmphdmFxAH4AGXEAfgAWcQB-ABdzcQB-AAwCAAACNnB0ABhqYXZhLmxhbmcucmVmbGVjdC5NZXRob2R0AAtNZXRob2QuamF2YXEAfgAZcQB-ABZxAH4AF3NxAH4ADAEAAABrcQB-AA50ACJjb20uY2xvdWQudm0uVm1Xb3JrSm9iSGFuZGxlclByb3h5dAAaVm1Xb3JrSm9iSGFuZGxlclByb3h5LmphdmF0AA9oYW5kbGVWbVdvcmtKb2JwcHNxAH4ADAEAABX_cQB-AA5xAH4AD3EAfgAQcQB-ACNwcHNxAH4ADAEAAABmcQB-AA50ACBjb20uY2xvdWQudm0uVm1Xb3JrSm9iRGlzcGF0Y2hlcnQAGFZtV29ya0pvYkRpc3BhdGNoZXIuamF2YXQABnJ1bkpvYnBwc3EAfgAMAQAAAmxxAH4ADnQAP29yZy5hcGFjaGUuY2xvdWRzdGFjay5mcmFtZXdvcmsuam9icy5pbXBsLkFzeW5jSm9iTWFuYWdlckltcGwkNXQAGEFzeW5jSm9iTWFuYWdlckltcGwuamF2YXQADHJ1bkluQ29udGV4dHBwc3EAfgAMAQAAADBxAH4ADnQAPm9yZy5hcGFjaGUuY2xvdWRzdGFjay5tYW5hZ2VkLmNvbnRleHQuTWFuYWdlZENvbnRleHRSdW5uYWJsZSQxdAAbTWFuYWdlZENvbnRleHRSdW5uYWJsZS5qYXZhdAADcnVucHBzcQB-AAwBAAAAN3EAfgAOdABCb3JnLmFwYWNoZS5jbG91ZHN0YWNrLm1hbmFnZWQuY29udGV4dC5pbXBsLkRlZmF1bHRNYW5hZ2VkQ29udGV4dCQxdAAaRGVmYXVsdE1hbmFnZWRDb250ZXh0LmphdmF0AARjYWxscHBzcQB-AAwBAAAAZnEAfgAOdABAb3JnLmFwYWNoZS5jbG91ZHN0YWNrLm1hbmFnZWQuY29udGV4dC5pbXBsLkRlZmF1bHRNYW5hZ2VkQ29udGV4dHEAfgAzdAAPY2FsbFdpdGhDb250ZXh0cHBzcQB-AAwBAAAANHEAfgAOcQB-ADZxAH4AM3QADnJ1bldpdGhDb250ZXh0cHBzcQB-AAwBAAAALXEAfgAOdAA8b3JnLmFwYWNoZS5jbG91ZHN0YWNrLm1hbmFnZWQuY29udGV4dC5NYW5hZ2VkQ29udGV4dFJ1bm5hYmxlcQB-AC9xAH4AMHBwc3EAfgAMAQAAAjhxAH4ADnEAfgAqcQB-ACtxAH4AMHBwc3EAfgAMAgAAAgNwdAAuamF2YS51dGlsLmNvbmN1cnJlbnQuRXhlY3V0b3JzJFJ1bm5hYmxlQWRhcHRlcnQADkV4ZWN1dG9ycy5qYXZhcQB-ADRxAH4AFnEAfgAXc3EAfgAMAgAAAQhwdAAfamF2YS51dGlsLmNvbmN1cnJlbnQuRnV0dXJlVGFza3QAD0Z1dHVyZVRhc2suamF2YXEAfgAwcQB-ABZxAH4AF3NxAH4ADAIAAARocHQAJ2phdmEudXRpbC5jb25jdXJyZW50LlRocmVhZFBvb2xFeGVjdXRvcnQAF1RocmVhZFBvb2xFeGVjdXRvci5qYXZhdAAJcnVuV29ya2VycQB-ABZxAH4AF3NxAH4ADAIAAAJ0cHQALmphdmEudXRpbC5jb25jdXJyZW50LlRocmVhZFBvb2xFeGVjdXRvciRXb3JrZXJxAH4ARXEAfgAwcQB-ABZxAH4AF3NxAH4ADAIAAAM9cHQAEGphdmEubGFuZy5UaHJlYWR0AAtUaHJlYWQuamF2YXEAfgAwcQB-ABZxAH4AF3NyAB9qYXZhLnV0aWwuQ29sbGVjdGlvbnMkRW1wdHlMaXN0ergXtDynnt4CAAB4cHgAABCadwgAAAAAAAAAAHg >> > 2021-05-28 09:00:44,521 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] >> > (Work-Job-Executor-3:ctx-1aea8c24 job-135/job-136 ctx-f15549a6) >> > (logid:8bef4350) Publish async job-136 complete on message bus >> > >> > Side note: I see errors for ghost/missing VM instances. I thought that >> > was resolved with 4.15. >> > Unable to find matched VM in CloudStack DB. name: >> > ffe8ca8a-4c58-4c47-b93d-c524f90453cf >> > >> > Many thanks for your eyes on this! >> > >> > Mike >> > >> > >> > >> > >> > -----Original Message----- >> > From: Corey, Mike >> > Sent: Thursday, May 27, 2021 1:54 PM >> > To: [email protected] >> > Subject: RE: VMware Instance Error >> > >> > Still having similar issues with the 530 error in the UI when deploying >> an >> > instance. It doesn't look to be specific to Win10. I uploaded a CentOS >> > template and am receiving the same 530 error in the UI. Again, nothing >> in >> > the log indicates an exact issue/error... >> > >> > Is this permissions issue on the tmpl/x folder or something? It seems >> > like no matter what I set the UI upload (example HVM option unchecked) >> the >> > XML and template properties file both have HVM true. >> > >> > What occurs at template upload to ACS that "reads the OVF" and adds the >> > settings on the template? Again, the settings tab for all the templates >> > I've uploaded are blank-no settings added by ACS. >> > >> > 021-05-27 13:38:47,501 DEBUG [c.c.a.m.AgentManagerImpl] >> > (AgentManager-Handler-3:null) (logid:) SeqA 4-36204: Sending Seq >> 4-36204: >> > { Ans: , MgmtId: 345050012965, via: 4, Ver: v1, Flags: 100010, >> > >> [{"com.cloud.agent.api.AgentControlAnswer":{"result":"true","wait":"0"}}] } >> > 2021-05-27 13:38:54,670 DEBUG [c.c.a.ApiServlet] >> > (qtp1026871825-13:ctx-cfe459fc) (logid:6271904e) ===START=== -- GET >> > >> zoneid=1cf90fc6-1ae5-416f-a2b4-672176740ecb&templateid=323c0a0f-fb34-41ef-932a-146454df381c&serviceofferingid=620aa542-56e8-4a1e-ba60-7c43fd31e717&affinitygroupids=&nicnetworklist[0].nic=8&nicnetworklist[0].network=62bfbed1-d07c-4886-b4f4-bf594543bb28&name=May27-CentOS-01&displayname=May27-CentOS-01&command=deployVirtualMachine&response=json >> > 2021-05-27 13:38:54,675 DEBUG [c.c.a.ApiServer] >> > (qtp1026871825-13:ctx-cfe459fc ctx-265c9f8c) (logid:6271904e) CIDRs from >> > which account 'Acct[a5f712c7-ac2e-11eb-b0fb-00505695799f-admin]' is >> allowed >> > to perform API calls: 0.0.0.0/0,::/0 >> > 2021-05-27 <http://0.0.0.0/0,::/02021-05-27> 13:38:54,684 TRACE >> > [o.a.c.a.c.u.v.DeployVMCmd] (qtp1026871825-13:ctx-cfe459fc ctx-265c9f8c) >> > (logid:6271904e) nic, '8', goes on net, >> > '62bfbed1-d07c-4886-b4f4-bf594543bb28' >> > 2021-05-27 13:38:54,689 DEBUG [c.c.u.AccountManagerImpl] >> > (qtp1026871825-13:ctx-cfe459fc ctx-265c9f8c) (logid:6271904e) Access >> > granted to Acct[a5f712c7-ac2e-11eb-b0fb-00505695799f-admin] to >> > >> org.apache.cloudstack.quota.vo.ServiceOfferingVO$$EnhancerByCGLIB$$f1711368@40f9eaf1 >> > by AffinityGroupAccessChecker >> > 2021-05-27 13:38:54,690 DEBUG [c.c.u.AccountManagerImpl] >> > (qtp1026871825-13:ctx-cfe459fc ctx-265c9f8c) (logid:6271904e) Access >> > granted to Acct[a5f712c7-ac2e-11eb-b0fb-00505695799f-admin] to null by >> > AffinityGroupAccessChecker >> > 2021-05-27 13:38:54,701 DEBUG [c.c.n.NetworkModelImpl] >> > (qtp1026871825-13:ctx-cfe459fc ctx-265c9f8c) (logid:6271904e) Service >> > SecurityGroup is not supported in the network id=204 >> > 2021-05-27 13:38:54,708 DEBUG [c.c.u.d.T.Transaction] >> > (qtp1026871825-13:ctx-cfe459fc ctx-265c9f8c) (logid:6271904e) Rolling >> back >> > the transaction: Time = 1 Name = qtp1026871825-13; called by >> > >> -TransactionLegacy.rollback:888-TransactionLegacy.removeUpTo:831-TransactionLegacy.close:655-Transaction.execute:38-UserVmManagerImpl.commitUserVm:3970-UserVmManagerImpl.commitUserVm:4157-UserVmManagerImpl.createVirtualMachine:3865-UserVmManagerImpl.createAdvancedVirtualMachine:3391-UserVmManagerImpl.createVirtualMachine:5315-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:62-DelegatingMethodAccessorImpl.invoke:43 >> > 2021-05-27 13:38:54,708 ERROR [c.c.a.ApiServer] >> > (qtp1026871825-13:ctx-cfe459fc ctx-265c9f8c) (logid:6271904e) unhandled >> > exception executing api command: [Ljava.lang.String;@29871d71 >> > java.lang.NullPointerException >> > at >> > >> com.cloud.vm.UserVmManagerImpl$4.doInTransaction(UserVmManagerImpl.java:4034) >> > at >> > >> com.cloud.vm.UserVmManagerImpl$4.doInTransaction(UserVmManagerImpl.java:3970) >> > at com.cloud.utils.db.Transaction.execute(Transaction.java:40) >> > at >> > com.cloud.vm.UserVmManagerImpl.commitUserVm(UserVmManagerImpl.java:3970) >> > at >> > com.cloud.vm.UserVmManagerImpl.commitUserVm(UserVmManagerImpl.java:4157) >> > at >> > >> com.cloud.vm.UserVmManagerImpl.createVirtualMachine(UserVmManagerImpl.java:3865) >> > at >> > >> com.cloud.vm.UserVmManagerImpl.createAdvancedVirtualMachine(UserVmManagerImpl.java:3391) >> > at >> > >> com.cloud.vm.UserVmManagerImpl.createVirtualMachine(UserVmManagerImpl.java:5315) >> > at >> > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native >> > Method) >> > at >> > >> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >> > at >> > >> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> > at java.base/java.lang.reflect.Method.invoke(Method.java:566) >> > at >> > >> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344) >> > at >> > >> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198) >> > at >> > >> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) >> > at >> > >> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:95) >> > at >> > >> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) >> > at >> > >> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212) >> > at com.sun.proxy.$Proxy177.createVirtualMachine(Unknown Source) >> > at >> > >> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.create(DeployVMCmd.java:719) >> > at >> > >> com.cloud.api.dispatch.CommandCreationWorker.handle(CommandCreationWorker.java:47) >> > at >> > com.cloud.api.dispatch.DispatchChain.dispatch(DispatchChain.java:37) >> > at >> > com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:88) >> > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:688) >> > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:588) >> > at >> > com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:321) >> > at com.cloud.api.ApiServlet$1.run(ApiServlet.java:134) >> > at >> > >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) >> > at >> > >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102) >> > at >> > >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) >> > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:131) >> > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:93) >> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:645) >> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:750) >> > at >> > >> org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1386) >> > at >> > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) >> > at >> > >> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:547) >> > at >> > >> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) >> > at >> > >> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:590) >> > at >> > >> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) >> > at >> > >> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) >> > at >> > >> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1610) >> > at >> > >> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) >> > at >> > >> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1300) >> > at >> > >> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) >> > at >> > >> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:485) >> > at >> > >> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1580) >> > at >> > >> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) >> > at >> > >> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1215) >> > at >> > >> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) >> > at >> > >> org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:767) >> > at >> > >> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146) >> > at >> > >> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) >> > at org.eclipse.jetty.server.Server.handle(Server.java:500) >> > at >> > >> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:383) >> > at >> > org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:547) >> > at >> > org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:375) >> > at >> > >> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:273) >> > at org.eclipse.jetty.io >> > .AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) >> > at org.eclipse.jetty.io >> > .FillInterest.fillable(FillInterest.java:103) >> > at >> > >> org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:543) >> > at >> > >> org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:398) >> > at >> > >> org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:161) >> > at org.eclipse.jetty.io >> > .FillInterest.fillable(FillInterest.java:103) >> > at org.eclipse.jetty.io >> > .ChannelEndPoint$2.run(ChannelEndPoint.java:117) >> > at >> > >> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) >> > at >> > >> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) >> > at >> > >> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) >> > at >> > >> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) >> > at >> > >> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375) >> > at >> > >> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806) >> > at >> > >> org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938) >> > at java.base/java.lang.Thread.run(Thread.java:829) >> > 2021-05-27 13:38:54,713 DEBUG [c.c.a.ApiServlet] >> > (qtp1026871825-13:ctx-cfe459fc ctx-265c9f8c) (logid:6271904e) >> ===END=== -- >> > GET >> > >> zoneid=1cf90fc6-1ae5-416f-a2b4-672176740ecb&templateid=323c0a0f-fb34-41ef-932a-146454df381c&serviceofferingid=620aa542-56e8-4a1e-ba60-7c43fd31e717&affinitygroupids=&nicnetworklist[0].nic=8&nicnetworklist[0].network=62bfbed1-d07c-4886-b4f4-bf594543bb28&name=May27-CentOS-01&displayname=May27-CentOS-01&command=deployVirtualMachine&response=json >> > >> > Many thanks! >> > >> > >> > >> > -----Original Message----- >> > From: Corey, Mike >> > Sent: Friday, May 21, 2021 10:59 AM >> > To: [email protected] >> > Subject: RE: VMware Instance Error >> > >> > Okay - reran the deployment from "new" UI and it displays "Request >> Failed >> > (530) - Request failed with status code 530". >> > >> > This is ACS 4.15 deploying to vCenter 6.7 using a Windows10x64 image >> > template. Right now, I have global setting vmware.root.disk.controller >> as >> > blank. If I recall the previous build, I could set this setting at the >> > instance provision wizard. See anything below to indicate my hiccup? >> > >> > Logs below: >> > >> > 2021-05-21 10:39:05,421 DEBUG [c.c.a.ApiServlet] >> > (qtp1026871825-20:ctx-90b111cd) (logid:03c48de3) ===START=== 10.4.89.3 >> -- >> > GET >> > >> zoneid=1cf90fc6-1ae5-416f-a2b4-672176740ecb&podid=be90d04e-5257-43fb-97de-7727d10fae6a&clusterid=61445715-9baa-4768-863f-473652c324cc&hostid=7edc7494-a78f-4d72-8158-6dcbf7370f3f&templateid=1ada50d8-a523-4670-93c3-6d942169b7ae&serviceofferingid=5777d4fc-87b7-46c4-a253-4ff69f80b4ca&affinitygroupids=&nicnetworklist[0].nic=8&nicnetworklist[0].network=62bfbed1-d07c-4886-b4f4-bf594543bb28&name=CV-Test01&displayname=CV-Test01&command=deployVirtualMachine&response=json >> > 2021-05-21 10:39:05,427 DEBUG [c.c.a.ApiServer] >> > (qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) (logid:03c48de3) CIDRs from >> > which account 'Acct[a5f712c7-ac2e-11eb-b0fb-00505695799f-admin]' is >> allowed >> > to perform API calls: 0.0.0.0/0,::/0 >> > 2021-05-21 <http://0.0.0.0/0,::/02021-05-21> 10:39:05,462 TRACE >> > [o.a.c.a.c.u.v.DeployVMCmd] (qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) >> > (logid:03c48de3) nic, '8', goes on net, >> > '62bfbed1-d07c-4886-b4f4-bf594543bb28' >> > 2021-05-21 10:39:05,469 DEBUG [c.c.u.AccountManagerImpl] >> > (qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) (logid:03c48de3) Access >> > granted to Acct[a5f712c7-ac2e-11eb-b0fb-00505695799f-admin] to >> > >> org.apache.cloudstack.quota.vo.ServiceOfferingVO$$EnhancerByCGLIB$$f1711368@49f71a9e >> > by AffinityGroupAccessChecker >> > 2021-05-21 10:39:05,469 DEBUG [c.c.u.AccountManagerImpl] >> > (qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) (logid:03c48de3) Access >> > granted to Acct[a5f712c7-ac2e-11eb-b0fb-00505695799f-admin] to null by >> > AffinityGroupAccessChecker >> > 2021-05-21 10:39:05,493 DEBUG [c.c.n.NetworkModelImpl] >> > (qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) (logid:03c48de3) Service >> > SecurityGroup is not supported in the network id=204 >> > 2021-05-21 10:39:05,506 DEBUG [c.c.u.d.T.Transaction] >> > (qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) (logid:03c48de3) Rolling >> back >> > the transaction: Time = 3 Name = qtp1026871825-20; called by >> > >> -TransactionLegacy.rollback:888-TransactionLegacy.removeUpTo:831-TransactionLegacy.close:655-Transaction.execute:38-UserVmManagerImpl.commitUserVm:3970-UserVmManagerImpl.commitUserVm:4157-UserVmManagerImpl.createVirtualMachine:3865-UserVmManagerImpl.createAdvancedVirtualMachine:3391-UserVmManagerImpl.createVirtualMachine:5315-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:62-DelegatingMethodAccessorImpl.invoke:43 >> > 2021-05-21 10:39:05,507 ERROR [c.c.a.ApiServer] >> > (qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) (logid:03c48de3) unhandled >> > exception executing api command: [Ljava.lang.String;@32b6d5fc >> > java.lang.NullPointerException >> > at >> > >> com.cloud.vm.UserVmManagerImpl$4.doInTransaction(UserVmManagerImpl.java:4034) >> > at >> > >> com.cloud.vm.UserVmManagerImpl$4.doInTransaction(UserVmManagerImpl.java:3970) >> > at com.cloud.utils.db.Transaction.execute(Transaction.java:40) >> > at >> > com.cloud.vm.UserVmManagerImpl.commitUserVm(UserVmManagerImpl.java:3970) >> > at >> > com.cloud.vm.UserVmManagerImpl.commitUserVm(UserVmManagerImpl.java:4157) >> > at >> > >> com.cloud.vm.UserVmManagerImpl.createVirtualMachine(UserVmManagerImpl.java:3865) >> > at >> > >> com.cloud.vm.UserVmManagerImpl.createAdvancedVirtualMachine(UserVmManagerImpl.java:3391) >> > at >> > >> com.cloud.vm.UserVmManagerImpl.createVirtualMachine(UserVmManagerImpl.java:5315) >> > at >> > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native >> > Method) >> > at >> > >> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >> > at >> > >> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> > at java.base/java.lang.reflect.Method.invoke(Method.java:566) >> > at >> > >> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344) >> > at >> > >> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198) >> > at >> > >> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) >> > at >> > >> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:95) >> > at >> > >> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) >> > at >> > >> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212) >> > at com.sun.proxy.$Proxy177.createVirtualMachine(Unknown Source) >> > at >> > >> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.create(DeployVMCmd.java:719) >> > at >> > >> com.cloud.api.dispatch.CommandCreationWorker.handle(CommandCreationWorker.java:47) >> > at >> > com.cloud.api.dispatch.DispatchChain.dispatch(DispatchChain.java:37) >> > at >> > com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:88) >> > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:688) >> > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:588) >> > at >> > com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:321) >> > at com.cloud.api.ApiServlet$1.run(ApiServlet.java:134) >> > at >> > >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) >> > at >> > >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102) >> > at >> > >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) >> > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:131) >> > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:93) >> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:645) >> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:750) >> > at >> > >> org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1386) >> > at >> > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) >> > at >> > >> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:547) >> > at >> > >> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) >> > at >> > >> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:590) >> > at >> > >> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) >> > at >> > >> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) >> > at >> > >> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1610) >> > at >> > >> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) >> > at >> > >> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1300) >> > at >> > >> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) >> > at >> > >> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:485) >> > at >> > >> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1580) >> > at >> > >> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) >> > at >> > >> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1215) >> > at >> > >> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) >> > at >> > >> org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:767) >> > at >> > >> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146) >> > at >> > >> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) >> > at org.eclipse.jetty.server.Server.handle(Server.java:500) >> > at >> > >> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:383) >> > at >> > org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:547) >> > at >> > org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:375) >> > at >> > >> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:273) >> > at org.eclipse.jetty.io >> > .AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) >> > at org.eclipse.jetty.io >> > .FillInterest.fillable(FillInterest.java:103) >> > at >> > >> org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:543) >> > at >> > >> org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:398) >> > at >> > >> org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:161) >> > at org.eclipse.jetty.io >> > .FillInterest.fillable(FillInterest.java:103) >> > at org.eclipse.jetty.io >> > .ChannelEndPoint$2.run(ChannelEndPoint.java:117) >> > at >> > >> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) >> > at >> > >> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) >> > at >> > >> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) >> > at >> > >> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) >> > at >> > >> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375) >> > at >> > >> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806) >> > at >> > >> org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938) >> > at java.base/java.lang.Thread.run(Thread.java:829) >> > 2021-05-21 10:39:05,514 DEBUG [c.c.a.ApiServlet] >> > (qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) (logid:03c48de3) ===END=== >> > 10.4.89.3 -- GET >> > >> zoneid=1cf90fc6-1ae5-416f-a2b4-672176740ecb&podid=be90d04e-5257-43fb-97de-7727d10fae6a&clusterid=61445715-9baa-4768-863f-473652c324cc&hostid=7edc7494-a78f-4d72-8158-6dcbf7370f3f&templateid=1ada50d8-a523-4670-93c3-6d942169b7ae&serviceofferingid=5777d4fc-87b7-46c4-a253-4ff69f80b4ca&affinitygroupids=&nicnetworklist[0].nic=8&nicnetworklist[0].network=62bfbed1-d07c-4886-b4f4-bf594543bb28&name=CV-Test01&displayname=CV-Test01&command=deployVirtualMachine&response=json >> > >> > -----Original Message----- >> > From: Corey, Mike <[email protected]> >> > Sent: Friday, May 21, 2021 7:50 AM >> > To: [email protected] >> > Subject: [CAUTION] RE: VMware Instance Error >> > >> > Understood. I only tried the old UI because the instance deployment >> > failed under the new UI and there wasn't a specific error thrown to >> hint at >> > an issue. >> > >> > I'll try again today and dig through the logs and come back with >> findings. >> > >> > MC >> > >> > -----Original Message----- >> > From: Andrija Panic <[email protected]> >> > Sent: Thursday, May 20, 2021 5:47 PM >> > To: users <[email protected]> >> > Subject: Re: VMware Instance Error >> > >> > Hi Mike, >> > >> > that is expected in the old UI - at some point, new features were (in >> UI) >> > supported only for the new UI and not in old UI - so this failure is >> > expected/fine (I'm aware of the specific feature that is being >> > used/throwing an error here) >> > >> > Get over the old UI, I know there are emotional connections (for me at >> > least) and use just the new UI :) >> > >> > Best, >> > >> > On Thu, 20 May 2021 at 22:57, Corey, Mike <[email protected]> >> > wrote: >> > >> > > I'm having a VM instance fail and I can't pinpoint the issue. Maybe >> > > someone has seen this error below - I see it at the legacy UI and not >> on >> > > the new UI. The new UI just fails the instance after the VM is >> created >> > in >> > > vCenter. >> > > >> > > >> > > >> > > "Boot type and boot mode are not supported on VMware, as we honour >> what >> > is >> > > defined in the template." >> > > >> > > >> > > >> > > I thought it was the global setting vmware.root.disk.controller - I >> had >> > it >> > > as osdefault (failed) scsi (failed) and blank (failed) - so I'm not >> sure >> > > where or what is triggering the error/failure. >> > > >> > > >> > > >> > > Many thanks! >> > > >> > > Mike >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > *Mike Corey* >> > > >> > > >> > > Technology Senior Consultant, IT CS CTW Operation & Virtualization >> > Service >> > > US >> > > >> > > >> > > *SAP AMERICA, INC.* 3999 West Chester Pike, Newtown Square, 19073 >> United >> > > States >> > > >> > > >> > > T +1 610 661 0905, M +1 484 274 2658, E [email protected] >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > >> > >> > -- >> > >> > Andrija Panic >> > >> >> >> -- >> >> Andrija Panić >> > -- Andrija Panić
