Rubrik discovery - WindowsCluster CIs are populated into table Windows ServerDescriptionDue to limitation of the Rubrik REST API call for "Rubrik Hosts" returning insufficient data for Windows Cluster CIs, these CIs were populated into Windows Server table (cmdb_ci_win_server) causing duplicate records, which already exists under cmdb_ci_cluster. The limitation is affecting also MSSQL Instances and MSSQL databases, associated with the Windows Cluster CIs in the Rubrik context. As part of previous implementation, the Rubrik REST API for "MSSQL Instances" and "MSSQL DBs" is returning Instances and associated Data bases related to Windows Clusters. From other side the Rubrik REST API for "WIndows Clusters" is returning insufficient data for those CIs, which cannot be uniquely identified. The data for Windows Clusters is populated into the CMDB table for Windows Servers, which is leading to duplicate CIs in different CMDB tables (cmdb_ci_cluster and cmdb_ci_win_server).Steps to Reproduce 1. Configure Rubrik discovery schedule of type serverless. Make sure credentials of type "Basic Auth" are configured associated to the Rubrik cluster.2. Execute discovery, make sure pattern "Rubrik Windows Host (LP)" is triggered and populating data into table "cmdb_ci_win_server".3. Observe that in table "cmdb_ci_win_server" CIs with Operating system type "WindowsCluster" are populated.WorkaroundDue to the issue described above, information for Windows Clusters is not retrieved and respectively they are not populated as CIs into the CMDB. Also MSSQL Instances and MSSQL Data bases, associated with Windows Clusters are filtered out from the discovery into the Rubrik context. This issue is fixed as part of PRB1503346 // DEF0217774 related to plugin 'Discovery and Service Mapping Patterns' version 1.0.81Related Problem: PRB1503346