Duplicate ESX server records created when the correlation_id of the ESX server changes - Known Error

Duplicate ESX server records created when the correlation_id of the ESX server changes Description There is an ESX server with correlation_id, mor_id, vcenter_uuid, and serial number in the cmdb_ci_esx_server table. When the ESX server's correlation_id changes, after Discovery, duplicate records can appear in the table with different correlation_id but with the same mor_id, vcenter_uuid, and serial number

Steps to Reproduce

1. Discover a vCenter

2. Make sure the ESX records are populated in the cmdb_ci_esx_server table

3. The correlation_id of the ESX server may change due to various reasons.

4. Discover the same vCenter once the correlation_id changes (Make sure that the MOR ID and the vCenter UUID of the ESX server do not change)

5. Duplicate ESX records are created in the cmdb_ci_esx_server table with different correlation_id

Workaround The issue is fixed in PRB1411817 in the Quebec release. The update set is attached to the PRB. After applying the update set, ESX servers will be identifiable by MOR ID and vCenter UUID if the install status is "Installed" or "In Maintenance". The records with install status "Installed" or "In Maintenance" are queried because other install statuses such as 'Retired' may indicate that the MOR ID has been recycled.