OCI cloud discovery

pratiksha5
Mega Sage

I am setting up OCI cloud discovery. The service account is validated and I have created schedule. The schedule to check datacenter is working fine. But the after schedule to discover the VM is getting canceled.

 

Error : The Discovery range is empty. 

 

 

 

 

 

1 ACCEPTED SOLUTION

pratiksha5
Mega Sage

I found KB in ServiceNow support. 

 

KB0998783 

 

Oracle OCI Cloud Schedule - VM Schedule is not supported

 

Oracle OCI Cloud Schedule - VM Schedule is not supported for now.

 

If this feature is required by your business, we recommend you to follow KB below to submit your requirements to our IDEA Management portal, so that our developers will assess and may add it as an OOB feature in the future:

 

View solution in original post

11 REPLIES 11

pratiksha5
Mega Sage

I found KB in ServiceNow support. 

 

KB0998783 

 

Oracle OCI Cloud Schedule - VM Schedule is not supported

 

Oracle OCI Cloud Schedule - VM Schedule is not supported for now.

 

If this feature is required by your business, we recommend you to follow KB below to submit your requirements to our IDEA Management portal, so that our developers will assess and may add it as an OOB feature in the future:

 

Hello Pratiksha,

 

We are facing the same IP range is empty error in our OCI VM schedules. Did you find a solution for the same?

 

Thanks & Regards,

Shilpa Wadhwani

VM Schedule is not supported for OCI. 

 

Check the link https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0998783

 

 

You can to IP based discovery to discover the configuration items

 

Thanks for your answer Pratiksha. I have two follow up questions:

 

1. Were you able to discover the CIs by manually running schedules on the IP addresses of the VMs?

2. Do we require a mid server to execute an OCI Cloud schedule?

Look closely into the cloud discovery logs. (Oracle OCI - Virtual Machine (LP)) this pattern will help you to discover the VMS. This one run as part of the cloud discovery schedule only. You might see some error in the logs which says maximum pattern count reached. Update this property "glide.discovery.pattern.orchestrator.max_patterns_triggered" to a higher number (390) worked for me. (best of luck) (Mark my answers helpful if they helped you in anyway)