Duplicate cmdb_serial_number Records and Multiple Reconcile Duplicate Tasks Created During Parallel Discovery - Known Error

Duplicate cmdb_serial_number Records and Multiple Reconcile Duplicate Tasks Created During Parallel Discovery Description During a discovery run, parallel discovery workers insert the same physical serial number into the cmdb_serial_number lookup table, resulting in duplicate serial number records despite IRE’s de‑duplication logic. The race condition also causes three identical reconcile_duplicate_task records to be created on a subsequent discovery run. These duplicates block proper identification and generate confusing duplicate‑task entries, affecting the accuracy of the CMDB and subsequent discovery processing.

Steps to Reproduce

1. Run a discovery that uses a Network Switch pattern with parallel sensor jobs enabled. 2. Ensure the same physical switch is reachable via multiple IP addresses so that separate discovery workers process the same device concurrently. 3. Observe that each worker submits an IRE payload containing the same cmdb_serial_number lookup (e.g., serial ABCD, type physical). 4. Verify that duplicate entries appear in the cmdb_serial_number table and that multiple reconcile_duplicate_task records are created during the follow‑on discovery.

Workaround 1. Delete one of the duplicate cmdb_serial_number records, retaining the correct one. 2. Close or cancel duplicate reconcile_duplicate_task records. 3. (Optional) Reduce the parallelism of the Network Switch discovery pattern by lowering max_threads or max_pages_per_sensor to minimize concurrent processing of the same CI.