Cluster node's data (cmdb_ci_storage_cluster_node) is not getting updated through discovery - EMC IsilonDescriptionThis defect can be reproduced in environments with more than one storage cluster. EMC Isilon Pattern does not create meaningful names for storage cluster nodes (cmdb_ci_storage_cluster_node). After Discovery storage nodes are named "1", "2", "3"... In the next discovery of the Storage cluster, nodes are getting identified by name, and their creation is skipped. Just relation is modified. After discovery on all Storage clusters, you can see that all cluster nodes are attached just to one storage cluster. In every new discovery run on one of the storage clusters cluster nodes are attaching to that cluster on which discovery is performed, and detaching from the previous.### Affected version(s):Orlando Patch 4bThere is a problem reported for a similar issue - PRB1404866 and it is related to names for storage node elements. Steps to Reproduce 1. Open OOTB instance 2. Do discovery on one storage cluster, all nodes can be seen in a related list3. Do discovery on another cluster, all nodes can bee seen in the related list, but they are nodes detached from the cluster discovered in step 2. WorkaroundChange the identifier rule for the cluster node table by adding serial-number attribute along with the name. serial_number is unique for every node so it would help to uniquely identify the nodes Related Problem: PRB1432052