Duplicate VirtualMachine (same name).

To list dup VirtualMachine, execute the query below. The raws with a count >=2 denotes duplicates (same name)

search VirtualMachine show name process with countUnique(0)
search VirtualMachine show short_name process with countUnique(0)

Cause 1: The hypervisors where scanned using difference scopes.

To confirm:

If 2 duplicated VirtualMachined are linked to 2 distinct hypervisor Host nodes, the cause is possible.

If the hypervisors Hosts are duplicated too, the cause is possible

The scope is visible in the DiscoveryRun of the duplicated hypervisors Hosts. If the scope is not always the same, the cause is confirmed.

Workaround: Delete the hypervisor Hosts and use the solution below 
Solution: Use a single scope.

Cause 2: (not confirmed) Some hypervisors are scanned by scanners while they used to be scanned by their consolidator.

To confirm: 

If the duplicates are only visible in the consolidator, the cause is possible.

If the duplicates are linked to the same hypervisor Host, the cause is confirmed.

If the duplicates all are aging excepted 1 VirtualMachine node, the cause is possible.

Workaround:

1- Keep scanning the hypervisors until the transient duplicates age out
or
2- manually delete the hypervisor host and rescan them from the scanner
or
3- manually delete the duplicates from the consolidator with an age_count < 0 

Cause 3: (not confirmed) The hypervisors were rescanned with new pattern that assigned a different key to the nodes.

To confirm: 

If the duplicates are linked to the same hypervisor Host, the cause is possible.

If the duplicates all are aging excepted 1 VirtualMachine node, the cause is possible.
If the first occurrence happens after a pattern change (customization or TKU upgrade), the cause is possible.

Workaround: Use the workaround of the cause above.

Cause 4: The vm was moved to another hypervisor. Its new hypervisor reports important changes in the vm (new uuid, new serial ....)

To confirm:

If 2 duplicated VirtualMachined are linked to 2 distinct hypervisor Host nodes, the cause is possible.

If the creation of new duplicated node is correlated with move (vmMove vcenter event?), the cause is probable.

Workaround: Use the workaround of the cause above.