WeCloud

UI Error : java.lang.NullPointerException: uuid Error in the logs : 2018-11-01 11:33:55,446 | DEBUG | pool-jetty-81 | ExceptionHandlerAdvice | Handling unmapped exception | requestId=8aeb2135-78a0-447f-901f-aa46c02b13ad,request=PUT https://cloud com/network/firewall/globalroot-0/config/layer3sections/ce30a14f-8703-4aeb-a444-e17e81a4b402,requestTime=1541025233061,remoteAddress=10.10.10.200:35941,userAgent=Mozilla/5.0 (Macintosh; Intel Mac O S X 10_14_0) AppleWebKit/5...,accept=application/xml java.lang.NullPointerException: uuid         at com.vmware.vcloud.common.model.BaseObjectId.from(BaseObjectId.java:103)         at com.vmware.ssdc.backend.services.impl.VmManagerImpl.getVAppVmModel(VmManagerImpl.java:526)         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso

Symptoms : java.lang.NullPointerException Unable to deploy a VM in only one vApp  It didn't matter which template I use. The same template works fine in another vApp in the same OrgVDC  The error NullPointerException is quite generic with vCloud director and this is mostly due to a stale/invalid entry in the vCloud director database.  Analysis :  The vCloud-container-debug.log failed with the below java.lang.NullPointerException              at com.vmware.vcloud.common.validate.impl.VmLimitsValidatorImpl.validateVmDisks(VmLimitsValidatorImpl.java:159) After checking a bit more in the logs just above the error, I found that vCD was unable to query a VM storage information.  In my case, it was ' IncomeOnline-Rock_DeleteOn ' with moref  vm-3055.  The vm did not exist in my vCenter and was part of the same vApp in vCD where I have deployment (VM creation) issue.  Fix  :   Deleted the VM named ' IncomeOnline-Rock_Delete

I deployed a new vCloud director 9.7 and the VM console fails to connect even though the certificates and URLs are updated correctly in Public Addresses. The chrome browser console (ctrl+shift+j) fails like below :  failed: Error during WebSocket handshake: Unexpected response code: 404 After reading the VMware documentation which says " For an installation with a single IP address, you can customize the console proxy address from the  vCloud Director  Web Console. For example, for the  vCloud Director  appliance, you must customize the console proxy address to  vcloud.example.com :8443 " From vCloud director 9.7, the second network (eth1) is dedicated to vpostgres database and console proxy uses (eth0) with a custom port 8443 Fix :  Update the console proxy address with custom port 8443 under vCD portal --> Administrator --> Public addresses Tadaa!  Thanks for reading. Hope it helps :)