Azure CI Discovery Error - discovery range is empty

[Harikumar V]

Hi Everyone,

We currently having the discovery scheduled for discovering the Azure VMs and Servers. When the schedule is running, the VM schedule is getting executed successfully but the child schedule (one that is executed once the VM scheduled is completed) for discovering the server is getting cancelled and having the error "discovery range is empty". Could you please let me know what is the root cause for it?

NOTE: We also have other schedule for different subscription in same Azure environment and we are not facing this error in other schedules.

Thanks,

Hari

[rhtmalik931]

Hello Harikumar,

have you come across any solution for this issue. I am also facing the same issue.

For some of VM schedules, discovery is working fine but for some discovery is getting cancelled with error "Discovery range is empty".

Please let me know if you have find solution for this.

[Harikumar V · Accepted solution]

Hi Everyone,

We faced this issue because there is an exception in selecting the MID server from the cluster configuration. The issue is resolved once the schedule is recreated with the correct MID server cluster.

[Vini]

Hi Hari,

We had same issue and I was able to find the workaround/solution for it.

Resolution# VM schedule should automatically pick up the subnets from OCI cloud Subnets table and added those subnets to VM schedule. but that’s not happening now.

Workaround# go to Cloud Subnets  (cmdb_ci_cloud_subnet) table there must be subnets discovered by cloud, export those manually and added those subnets into VM schedule, then run VM schedule job. 

Hope this help, if so please mark it to Helpful / Accept this solution. Thank you in Advance.