Discovery schedule created from one Service account triggers disocovery of multiple Service accounts - Support and Troubleshooting

Discovery schedule created from one Service account triggers disocovery of multiple Service accounts Issue In Cloud discovery, by design one Service account can have relationships to multiple LDC (Logical Data Centers), but one LDC can be related to just one Service account. That means LDC only belongs to that single account.

: : is triplet which uniquely identify discovered resource.

The first pattern which is run in discovery gets Logical Datacenter (e.g. in OpenStack discovery: OpenStack - Get Logical Datacenters ), and performs refresh datacenters for accounts. As a result, related datacenters to Service Account should be returned.

In case that discovery schedule created from one Service account triggers the discovery of multiple service accounts, there is a relation between the Logical Datacenter that belongs to the triggered account and another account. This can't be created by OOTB discovery.

Additional (more than one) Service Account can be manually added (relationship created) to LDC. That relationship will trigger new discoveries for the added Service account.

Release Any

Cause Relationships between one LDC and multiple Service Accounts can't be created by OOTB discovery setup.

As explained above, the manual creation of relationships can cause this behavior.

Another way of triggering something similar is the customization of identifiers.

In this particular case, a custom Independent identifier on cmdb_ci_openstack_datacenter table was created.

Resolution : : is triplet which uniquely identifies a discovered resource, hence identifier for LDC and resource has to be dependent on Cloud Service Account.

Verify that:

1. Identifiers are OOTB

2. Relationships between and