Rubrik discovery source causes CI class flipping for various OS Servers typesDescription Due to limitation of the Rubrik REST API calls used in discovery patterns "Rubrik Fileset (LP)", "Rubrik MSSQL Instance (LP)", "Rubrik Oracle DB (LP)" and "Rubrik Volume Group (LP)" returning insufficient data for the parent Host/Server CIs to which these CI types are dependent, these Host/Server CIs records are populated into Server table (cmdb_ci_server) causing flapping of the Class attribute for those CIs during the Rubrik discovery context from the respective operating system type to Server. In order the following relations between CI types to be created into the Rubrik discovery context: "cmdb_ci_server Owns::Owned by cmdb_ci_rubrik_volume_group" "cmdb_ci_db_mssql_instance Runs on::Runs cmdb_ci_server" "cmdb_ci_server Owns::Owned by cmdb_ci_rubrik_fileset" "cmdb_ci_db_ora_instance Runs on::Runs cmdb_ci_server" without information for the Server/Host CI, such as Serial Number, Serial Number Type, OS and OS Type returned from the response of the Rubrik REST APIs into the context of the Rubrik related discovery, the parent class - "cmdb_ci_server" is used in order duplicate CI creation to be avoided. As all the Operating System types Servers/Hosts (Windows, Linux, Solaris, AIX, HP-UX, etc.) are propagated to the parent class in this case "cmdb_ci_server". Due to the limitation described via the Rubrik REST API discovery source, the relations for the following CI Types are created with the parent server class - "cmdb_ci_server": Rubrik Fileset Rubrik MSSQL Instance Rubrik Oracle DB Rubrik Volume Group Due to the fact, anything rather than Host Name is returned by the vendor API (Rubrik) these patterns are causing the flapping of the Class name via Rubrik Discovery and IP based discovery: Rubrik Fileset (LP)Rubrik MSSQL Instance (LP)Rubrik Oracle DB (LP)Rubrik Volume Group (LP) The missing identifying attributes for the 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. Trigger the discovery schedule and verify that the following patterns are triggered: Rubrik Fileset (LP)Rubrik MSSQL Instance (LP)Rubrik Oracle DB (LP)Rubrik Volume Group (LP) and populating data into table "cmdb_ci_server" (Servers). 3. Observe that in table "cmdb_ci_server" CIs are being updated. - Sample response for Rubrik Volume Groups, where "hostname":"hostname.domain.com" is returned only, referring to Linux Server CI already discovered by IP based discovery:{"id":"VolumeGroup:::aaaaaaaa-bbbb-cccc-dddd-111111111111","name":"hostname.domain.com volumes","configuredSlaDomainId":"INHERIT","configuredSlaDomainName":"Inherit","configuredSlaDomainType":"ProtectionSla","primaryClusterId":"abcdefgh-1111-cccc-8888-123456789012","isConfiguredSlaDomainRetentionLocked":false,"effectiveSlaDomainId":"UNPROTECTED","effectiveSlaDomainName":"Unprotected","isEffectiveSlaDomainRetentionLocked":false,"effectiveSlaSourceObjectId":"VolumeGroup:::aaaaaaaa-bbbb-cccc-dddd-222222222222","effectiveSlaSourceObjectName":"slaname.domain.com","slaAssignment":"Unassigned","retentionSlaDomainId":"UNPROTECTED","hostname":"hostname.domain.com","hostId":"Host:::aaaaaaaa-bbbb-cccc-dddd-3333333333","isRelic":false,"forceFull":false}- Sample response for Rubrik MSSQL Instances where "rootName":"hostname3.domain.com" is returned only, referring to Windows Server CI already discovered by IP based discovery{"logBackupFrequencyInSeconds":3600,"logRetentionHours":500,"copyOnly":false,"id":"MssqlInstance:::aaaaaaaa-bbbb-cccc-dddd-111111111111","internalTimestamp":1643121336526000,"name":"MSSQLSERVER","primaryClusterId":"abcdefgh-1111-cccc-8888-123456789012","rootProperties":{"rootType":"Host","rootId":"Host:::aaaaaaaa-bbbb-cccc-dddd-222222222222","rootName":"hostname3.domain.com"},"protectionDate":"2019-11-31T15:15:49.459Z","version":"13.0.3202.5","configuredSlaDomainId":"aaaaaaaa-bbbb-cccc-dddd-3333333333","configuredSlaDomainType":"ProtectionSla","configuredSlaDomainName":"ProtectionSla","isRetentionLocked":false,"unprotectableReasons":[]}Into the official documentation link the following relations are mentioned, describing that scenario: https://docs.servicenow.com/bundle/sandiego-it-operations-management/page/product/service-mapping/reference/rubrik-discovery.html Workaround Due to the use case described above, discovery against the Server/Hosts CIs is recommended to be performed after the discovery of those CI types from the Rubrik discovery source. For the current moment this knowledge article has only informative character, as the use case described is due to vendor limitation. In order to keep the value for the operating system Class type as per regular IP based discovery source: 1. Verify you have discovered all the Server/Host CIs which are also part of the Rubrik context and they exists into the CMDB, under the respective classes. 2. Schedule the Rubrik discovery accordingly, verify the discovery from the Rubrik context is completed without any errors. 3. Schedule again regular IP based discvoery against the CIs where the Operating System class type has been changed.