INSERT INTO sa_ml_process_to_process errors seen when multiple Load Balancer records have the same source and target process - Known Error

INSERT INTO sa_ml_process_to_process errors seen when multiple Load Balancer records have the same source and target process Description In case of multiple Load Balancer records for the same source and target process the batch that updates LB records in P2P table fails with exception.

Steps to Reproduce

Run horizontal Discovery in the internal lab and create ML data on environment. Create TCP records for two LBs for the same IP:port and target Pool IP. Run following script as a background script, to reproduce the errors from the code responsible: var ptaLB = new ProcessToProcessLBAFPProviderEnhanced(); ptaLB.insertNextBatch(); Actual behaviour: An exception like this will be thrown:

Unique Key violation detected by database ((conn=596551) Duplicate entry 'de69d5ba87c616502b9eb88e8bbb35b2-c27ed4451bfd5a1051fefe25cc4b...' for key 'source_process_2') : com.glide.db.GlideSQLException: FAILED TRYING TO EXECUTE ON CONNECTION glide.14 (connpid=596551): INSERT INTO sa_ml_process_to_process

Expected behaviour: As these are not actually duplicates, because they have a different parent load balancer, the inserts should happen.

Workaround This problem has no workaround, is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.