In some cases, scan-cluster can create a duplicate entry for an existing cluster

[digimer]

Add a check to fix this when it happens (likely caused by connecting to a DB that hasn't been sync'ed yet).

[digimer]

@ylei-tsubame I've fixed the backend in 00fae9e. There's now two entries for 'an-anvil-01' and the UI seems to be picking the one that was deleted. Can you filter out any nodes whose scan_cluster_cib = DELETED.

[digimer]

Here is an example query;

SELECT 
    a.scan_cluster_name, 
    b.scan_cluster_node_name, 
    b.scan_cluster_node_pacemaker_id AS id, 
    b.scan_cluster_node_in_ccm AS in_ccm, 
    b.scan_cluster_node_crmd_member AS crmd, 
    b.scan_cluster_node_cluster_member AS member 
FROM 
    scan_cluster a, scan_cluster_nodes b 
WHERE 
    a.scan_cluster_uuid = b.scan_cluster_node_scan_cluster_uuid 
AND 
    a.scan_cluster_anvil_uuid = 'xxx' 
AND 
    a.scan_cluster_cib != 'DELETED';