Discovery of Windows Server in a Hyper V cluster failed due to duplicate records of cmdb_ci_hyper_v_cluster in the payloadDescriptionDiscovery of Windows Server in a Hyper-V cluster failed and the discovery status stays in "Identifying" node.From the discovery log, we can see the error message: "Failed Exploring CI Pattern, Pattern name: Windows OS - Servers".After enabling the Identification engine debug mode, we can see the following error:"identification_engine : DUPLICATE_PAYLOAD_RECORDS Found duplicate items in the payload (index xx and yy), using className [cmdb_ci_hyper_v_cluster] and fields [name]. "This is caused by "Hyper-V - Cluster" pattern used by "Windows OS - Servers" pattern failed to properly identify the cluster.Steps to Reproduce Create an infrastructure where you have multiple hypervisor server running on a cluster.Run discovery on one of the hypervisor server IP address.Check the discovery log to see that Windows OS - Servers pattern failed.Open the log and the pattern failed at "Check Output For Payload Errors" and the error message is: "Abandoned due to too many errors".Enable the identification engine debug mode (glide.discovery.debug.ci_identification = true) and you can find the following error in the system log:"identification_engine : DUPLICATE_PAYLOAD_RECORDS Found duplicate items in the payload (index xx and yy), using className [cmdb_ci_hyper_v_cluster] and fields [name].WorkaroundThis problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix. Temporary solution: Import attached xml file (sa_pattern_0aae04b59f6032001d753758442e70fd_workaround.xml) to your instance. This file will modify "Hyper-V - Cluster" shared library pattern.Related Problem: PRB1391972