Error: "Fenced vApp networks are not allowed in Org VDC" when copying a vApp

Products

• VMware Cloud Director

Issue/Introduction

• Trying to copy a vApps within fails with the error:
  
  [ ########-####-####-#########e43c ] Fenced vApp networks are not allowed in Org VDC '{Organization VDC Name}(com.vmware.vcloud.entity.vdc:########-####-####-#########908b)'


• The vApp was copied while Powered On.
• The vApp has a direct vApp network.
• The Organization VDC in which the vApp is deployed is backed by NSX that does not support fencing.

Environment

VMware Cloud Director 10.6

Cause

Cloning any Powered On vApp with a direct vApp networks will force the vApp network to be a fenced network to ensure that there are no conflicting IPs exists.

Resolution

In VMware Cloud Director 10.6.1 copying a vApp when Powered On is not allowed anymore.

Workaround

Option1
Copy a Powered ON vApp which has got Routed Network.

Option 2
If a vApp has a direct vApp network, then it needs to be Powered Off and then copied. After copying the vApp, before you power on both the vApp, ensure the IPs and Mac Addresses are not conflicting.