Deploy OVF from Content Library stuck At Network Step on VCSA (v6.7.0.40000)

[rsandbach]

After upgrading VCSA to v6.7.0.40000, I am no longer able to create new VMs from a template in a Content Library when using the customize os option.

A "Deploy OVF package from Content Library to Resource Pool" task starts after selecting the compute resource that never completes and I cannot proceed past the network selection step.

There are also javascript errors indicating a failure to populate the "IP Allocation Settings" due to a null reference. The network drop down populates, but the IP allocation section stays blank.

If I do not "customize" the os, I'm able to create the new VM. I can also deploy from a template in the datacenter and use the customize os option.

Any thoughts on how I can troubleshoot/which log files to look at specifically? Or is this possibly just a bug with the release.

[LokeshHK]

Did you change PNID of your VC after update?

refer to below KB in order to check whether you are facing the same issue or not?

VMware Knowledge Base

Regards

Lokesh

[rsandbach]

That doesn't seem to be the issue, as I am able to create new customization specs. However, I was able to find out that after clicking next,  the following error shows up in the log:

/var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log

Caused by: java.lang.NullPointerException: null

        at com.vmware.vsphere.client.provisioning.impl.ProvisioningMutationProvider.isIpPoolConfigurationValid(ProvisioningMutationProvider.java:250)

        at com.vmware.vsphere.client.provisioning.impl.ProvisioningMutationProvider.validate(ProvisioningMutationProvider.java:219)

This makes sense as the form is probably not passing any IP Pool information to the sever as it wasn't able to get this information itself.

Is there something new in vCenter/vSphere that requires additional configuration for the network?

[Robsewter]

Just want to add that you are not alone. I am seeing this in two environments that I have this set up in as well. Applied the latest v6.7.0.41000 patch and still the same issue. Didn't happen in v6.7.0.3.

[jasonboche]

Unfortunately I'm in the same boat across 4 environments all sharing a content library of templates. Software defined. Gotta love it.