"Duplicate key <IP>:<Port> (attempted merging values)" error when accessing the load balancing pool management page in VMware Cloud Director
search cancel

"Duplicate key <IP>:<Port> (attempted merging values)" error when accessing the load balancing pool management page in VMware Cloud Director

book

Article ID: 320451

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Symptoms:
The below error is displayed when accessing the load balancing pool management page in the UI:
  • Duplicate key xxx.xxx.xxx.xxx (attempted merging values com.vmware.nsxalb.dtos.inventory.PoolServerInventory@2b15356e and com.vmwarensxalb.dtos.inventory.PoolServerInventory@4ee4922a)
Similar log snippets in opt/vmware/vcloud-director/logs/vcloud-container-debug:
  • Failed to obtain busy lock on: xxx(com.vmware.vcloud.entity.gateway:xxx)
  • com.vmware.vcloud.common.persist.exception.DBDuplicateKeyException: ERROR: duplicate key value violates unique constraint "busy_object_pk"
      Detail: Key (object_type, object_id)=(43, xxx) already exists.


Environment

VMware Cloud Director 10.x

Cause

This issue occurs when you are attempting to make modifications to an Edge when it is still in the process of completing it's task, in this instance, waiting on feedback from NSX for the creation of the load balancing pool.
  • Cloud Director cannot merge the values as the gateway was busy when the tasks were set to run.
  • Cloud Director entity has been created but the pool is still not created in NSX-ALB, causing the pool_backing_id for the gateway_lb_pool table to be null in the Cloud Director database.

Resolution

This is a known issue affecting VMware Cloud Director 10.3.3.
The issue is resolved in VMware Cloud Director 10.3.3.4, available at Broadcom Downloads.
The issue is resolved in VMware Cloud Director 10.4.2, available at Broadcom Downloads.

Workaround:
To workaround this issue, please open a Support Request with VMware Technical Support and reference this KB article 320451.
Database modifications may be required to workaround this issue and will require VMware Technical Support assistance.