[ ########-####-####-############ ] Cannot delete organization VDC network <network-name> (urn:uuid:########-####-####-############) - Deletion of edge gateway <network-name> failed. - java.util.concurrent.ExecutionException: org.hibernate.jdbc.BatchedTooManyRowsAffectedException: Batch update returned unexpected row count from update [0]; actual row count: 2; expected: 1
Deletion of edge gateway failed.java.util.concurrent.ExecutionException: org.hibernate.jdbc.BatchedTooManyRowsAffectedException: Batch update returned unexpected row count from update [0]; actual row count: ; expected: .com.vmware.vcloud.dl.net.orgvdcnetwork.impl.OrgVdcNetworkManagerImpl.handleGatewayUpdateForIndependentNetwork(OrgVdcNetworkManagerImpl.java:806)Caused by: com.vmware.vcloud.dl.net.exception.NetworkInternalServerException: Deletion of edge gateway failed.java.util.concurrent.ExecutionException: org.hibernate.jdbc.BatchedTooManyRowsAffectedException: Batch update returned unexpected row count from update [0]; actual row count: ; expected: at com.vmware.vcloud.dl.net.gateway.impl.FabricGatewayManagerImpl.undeployGateway(FabricGatewayManagerImpl.java:274) at com.vmware.vcloud.dl.net.gateway.impl.FabricGatewayManagerImpl.undeployAndDeleteGateway(FabricGatewayManagerImpl.java:257)
/opt/vmware/vcloud-director/logs/vcloud-container-debug.log you see the message: Could not release IP/MAC while undeploying gateway <edge>[ ########-####-####-############ ] The entity <vapp-name> is in an invalid state for operation poweroff. - com.vmware.ssdc.util.LMException: Unable to stop network "<network-name>(urn:uuid:########-####-####-############)". - Deletion of edge gateway <network-name> failed. - java.util.concurrent.ExecutionException: org.hibernate.jdbc.BatchedTooManyRowsAffectedException: Batch update returned unexpected row count from update [0]; actual row count: 2; expected: 1This issue occurs during the database lookup for the gateway_assigned_mac in the database.
Cloud Director expects a unique MAC entry per Interface and will complain if there are more than 1 returned.
The workaround for this issue requires modification of the Cloud Director database.
For assistance, contact Broadcom Support and note this Article ID (382870) in the problem description. For more information, see Creating and managing Broadcom support cases .