Notifications

93 views

Description

Azure Discovery failed with below errors:

["ABANDONEDAbandoned due to too many errors","INVALID_INPUT_DATAFound invalid sys_id in payload. No record with sys_id [**********************] exist in table [cmdb_ci_azure_datacenter] or is a duplicate record with [discovery_source] 
field marked as Duplicate","ABANDONEDAbandoned due to too many errors"]
  • It is also observed

    • "cmdb_ci_azure_datacenter" table contains a Logical Datacenter with name "empty" 
    • localhost logs will indicate that the response processor has inserted a new record in Class:cmdb_ci_logical_datacenter

      [CMP API] com.snc.cloud.mgmt.modules.svccatalog.service.impl.ResponseProcessorImpl : Processing payload for error check [[Operation: NO_CHANGE, Class:cmdb_ci_cloud_service_account,
      SysId:xxxxxxxxxxxxxxxxxxxxx, Operation: INSERT, Class:cmdb_ci_logical_datacenter, SysId:xxxxxxxxxxxxxxxxxxxxx, Operation: INSERT, Class:cmdb_ci_resource_group, SysId:xxxxxxxxxxxxxxxxxxxxx]]

The issue is normally seen when an ARM template that contains a white space/Uppercase character in the value for location is used, for example, 'Southeast Asia' instead of southeastasia. In few cases, the issue was seen even when the ARM template had correct values for location but the cloud API response had whitespace in its value for Location.

Out of box, we have a response mapping record that maps location (source field) to object_id (Identifier CI class filed) of cmdb_ci_azure_datacenter (Identifier CI Class). If the response received via CAPI has a whitespace/uppercase character in the location field, this response mapping will cause the object_id of existing datacenter record to be updated with the new value (with space/uppercase). On a subsequent provisioning request, the response processor will not see a datacenter record (without space) and the identification engine will cause a blank datacenter record to be created with just the object_id field populated. Subsequent cloud discovery for Azure datacenter or provisioning requests can fail with Identification engine-related errors.

 

Steps to Reproduce

  1. Create an ARM template (cloud template) for a virtual machine with a white space in the value for the location, for example, 'Southeast Asia'
  2. Provision a cloud stack using this ARM template
  3. Once the provisioning is complete, navigate to list view of cmdb_ci_azure_datacenter and notice that the objec_id for datacenter 'southeastasia' is updated as 'Southeast Asia'
  4. Provision a new stack on Azure using a cloud catalog created using a simple blueprint
  5. Notice that a new datacenter record is inserted with a value for object_id populated (southeastasia) and all other fields empty.
  6. All subsequent provisioning requests/discovery will fails with identification engine related errors.

Workaround

This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available..

 

  1. Import the attached "Response_Mapping" update set.

    • The file includes a script which will remove whitespace from 'Location' and convert the characters to lowercase before updating the object_id field of azure datacenter record.

  2. Once imported the above-attached file, please use the process in the following documentation to ensure that the file upgrades when the instance is upgraded.

This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available..

 


Related Problem: PRB1363669

Seen In

SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - ITOM - Cloud Management Google Cloud Connector - v1.0
SR - ITOM - Cloud Management Terraform Connector - v1.1
SR - ITOM - CMDB CI Class Models - 201908
SR - ITOM - CMDB CI Class Models - 201909
SR - ITOM - Discovery and Service Mapping - 201908
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Intended Fix Version

Orlando

Fixed In

Madrid Patch 9
New York Patch 4

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-01-20 04:06:25
Published:2019-09-25