Upgrading from VMware NSX-T 3.1.x to 3.2.1 or 4.0.
During the upgrade, after the edges have been upgraded and before the managers upgrade has been completed, a new edge node was deployed and this operation failed with the following error:
“Host did not have any virtual network defined"
<DATE/TIME> INFO ActivityWorkerPool-1-8 VCExecuteOperationImpl 6439 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Retriving ConfigDataDto for cmPluginId xxxxxxxx-5799-46fb-bd59-xxxxxxxxxxxx
<DATE/TIME> INFO ActivityWorkerPool-1-8 VCExecuteOperationImpl 6439 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] CmPlugin response obtained for action [DeployOvf] of compute-manager: xxxxxxxx-5799-46fb-bd59-xxxxxxxxxxxx and request id: 71daab9f-7b5e-4968-8a21-6d461b3ef59c with status FAILED.
<DATE/TIME> ERROR ActivityWorkerPool-1-8 VCExecuteOperationImpl 6439 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP26070" level="ERROR" subcomp="manager"] CmPlugin execution of DeployOvf failed for compute-manager: xxxxxxxx-5799-46fb-bd59-xxxxxxxxxxxx with request id: 71daab9f-7b5e-4968-8a21-6d461b3ef59c
<DATE/TIME> ERROR ActivityWorkerPool-1-8 Vc60VmSfdmManager 6439 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP26065" level="ERROR" subcomp="manager"] Unable to deploy VM: NSX-Edge-01 on compute collection: Node/xxxxxxxx-4735-a5e7-xxxxxxxxxxxx
com.vmware.nsx.management.sfdm.exception.CmPluginExecutionFailed: Ovf deploy for vm NSX-Edge-01 failed on vc 10..x.x.x : Host did not have any virtual network defined.
at com.vmware.nsx.management.sfdm.vc.util.VCExecuteOperationImpl.logResponse(VCExecuteOperationImpl.java:1066) ~[libservice-fabric-installation.jar:?]
at com.vmware.nsx.management.sfdm.vc.util.VCExecuteOperationImpl.deployOvfTemplate(VCExecuteOperationImpl.java:366) ~[libservice-fabric-installation.jar:?]
at com.vmware.nsx.management.sfdm.vc.Vc60VmSfdmManager.deploy(Vc60VmSfdmManager.java:98) ~[libservice-fabric-installation.jar:?]
at com.vmware.nsx.management.sfm.deployment.service.DeploymentUnitActivityVMDeploy.phaseVMDeploy(DeploymentUnitActivityVMDeploy.java:215) ~[libservice-fabric-installation.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_332]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_332]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_332]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_332]
at com.vmware.nsx.management.container.activityframework.model.AbstractActivity.executePhase(AbstractActivity.java:147) ~[libnsx-framework.jar:?]
at com.vmware.nsx.management.container.activityframework.service.impl.ActivityExecutor.executeActivityPhase(ActivityExecutor.java:640) ~[libnsx-framework.jar:?]
This issue can also occur during an edge node redeployment at the same point in the upgrade.
This issue can occur when the edge OVF features of the new version are not backward compatible, so do not match what the current not upgraded manager version is.
Upgrades from NSX-T 3.2.1 onwards, edges nodes can be deployed or redeployed before managers are upgraded.
Workaround:
Deploy new edge node:
Redeploy failed edge node: