Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

OCI Cloud Discovery Failing at "Oracle OCI - Datacenter (LP)" with resource_response=[]

Shweta
Tera Contributor

Hi All,

I'm configuring ServiceNow OCI Cloud Discovery and facing an issue during datacenter discovery.

Current Status

  • MID Server is Up and Validated
  • MID Server capabilities = ALL
  • Oracle API Credential is configured successfully
  • Cloud Service Account validation is successful

Issue

Discovery fails in the following pattern: 

Oracle OCI - Datacenter (LP)
 
Error:
The API response is not valid. Failed Condition(s): [(${resource_response} : value=[]) IS NOT EMPTY ]
 
ECC Queue shows:
{
"status":"GRACEFUL_TERMINATION",
"results":{
"items":[],
"relations":[],
"references":[]
}
}
 

It appears the pattern executes successfully but receives an empty response (resource_response = []) when attempting to discover OCI datacenters/regions.

Has anyone encountered this issue before?

Specifically:

  • Are there any OCI permissions required beyond read all-resources in tenancy for Datacenter Discovery?
  • Does the OCI user need additional permissions to enumerate Regions or Availability Domains?
  • Are there any known issues with the Oracle OCI - Datacenter (LP) pattern in recent Discovery content versions?

Any guidance would be greatly appreciated.

Thanks,

Shweta

1 REPLY 1

skorukanti
Tera Contributor

Hi Shweta,

I came across the same issue once. In that case, we found that the specific OCI Service Account did not have any datacenters available to it.

It would be worth checking with your OCI team whether the particular Service Account being used for Discovery has any datacenters associated with it.

skorukanti_1-1788870382329.png

 

When there are no datacenters available for the Service Account, the API returns an empty response ([]). The OOB pattern then fails the validation because resource_response is empty and gracefully terminates without proceeding with the remaining steps.

So, based on my previous experience, this is expected OOB behavior and not necessarily a credential issue. The first thing I would verify is whether the Service Account actually has the required datacenter resource available to it.

Hope this helps. If this answers your question, please mark the response as helpful.

Thanks,
Sairam