AWS discovery fails with IRE error at containment/hosting rulesIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms The AWS discovery fails with the error at IRE. The Cloud API trails give the error as below. Error executing translator script :AWS Datacenter.List_Datacenters_Response_Processorcom.snc.cloud.mgmt.modules.cloudaccount.exception.CloudAccountException: There is no existing relationship between cmdb_ci_logical_datacenter and cmdb_ci_cloud_service_account The Syslog tables show the IRE errors as below identification_engine : Output = {"items":[{"className":"cmdb_ci_cloud_service_account","operation":"UPDATE","sysId":"28c69f84dbbdff006f7a96888a9619cf","identifierEntrySysId":"Unknown","identificationAttempts":[]},{"className":"cmdb_ci_aws_datacenter","operation":"UPDATE","sysId":"b9aab0dadbceff00038fc4048a961993","identifierEntrySysId":"Unknown","identificationAttempts":[]},{"className":"cmdb_ci_network","operation":"UPDATE","sysId":"4898a2a2db0233406f7a96888a961927","identifierEntrySysId":"39480c290be62200639be0d425673abe","identificationAttempts":[{"identifierName":"Network Rule","attemptResult":"MATCHED","attributes":["object_id"],"searchOnTable":"cmdb_ci_network"}]},{"sysId":"Unknown","identifierEntrySysId":"Unknown","errors":[{"error":"METADATA_RULE_MISSING","message":"No containment or hosting rules defined for dependent class [cmdb_ci_cloud_subnet]. Add containment/hosting rules for '{\"className\":\"cmdb_ci_cloud_subnet\",\"values\":{\"primary_dns\":\"\",\"discovery_source\":\"ServiceNow\",\"name\":\"WCS-InternalLoadbalancerSubnet-C\",\"cidr\":\"172.16.10.0/24\",\"state\":\"available\",\"available_ip_count\":\"250\",\"object_id\":\"subnet-c5975d9d\"}}'"},{"error":"ABANDONED","message":"Too many other errors"}],"identificationAttempts":[]},{"identifierEntrySysId":"Unknown","errors":[{"error":"INSERT_FAILED","message":"Insertion failed with error "}],"identificationAttempts":[{"identifierName":"Availibilty Zone Rule","attemptResult":"NO_MATCH","attributes":["object_id"],"searchOnTable":"cmdb_ci_availability_zone"}]}, Release Kingston P* & London P* Cause The missing Containment and Hosting rules cause the IRE to fail Resolution Refer below doc to add the Containment and Hosting rules according to the CI class in the error (As per above error, the issue is on cmdb_ci_cloud_subnet) Identification Engine MISSING_DEPENDENCY error Additional Information Sometimes, even after adding the required relations and containment hosting rules, the IRE still might fail with below errors. Previous error: (Solved by adding the above relations) {"error":"METADATA_RULE_MISSING","message":"No containment or hosting rules defined for dependent class [cmdb_ci_cloud_subnet] Current error: "{"error":"METADATA_RULE_MISSING","message":"No containment or hosting rules defined for dependent class [cmdb_ci_cloud_subnet]", is not present in latest discovery. Solution: Log into the instance Navigate >> cmdb_metadata_containment_list.do Compare the number of rules available from the instance in issue and OOB or where the issue not appearedCopy all the missing rules from OOB to the instance in the issue.