Fix for PRB1310988 breaks "Discover Virtual Machines" schedules for Master accounts - Known Error

Fix for PRB1310988 breaks "Discover Virtual Machines" schedules for Master accounts Description You note that the "Discover Virtual Machines" schedule that runs after Cloud Discovery does not discover all the VM IPs expected of member accounts when ran against a Master discovery schedule. Steps to Reproduce

Configure AWS/Azure Master account with no VMs in given LDC A.

Discover member(s) that have VMs in 'ON' state with public IP (or private IP after PP5) in LDC A.

Configure discovery schedule on master account to discover members for LDC A.

Run discovery schedule.

Note that when VM IP schedule runs it throws error as 'Range is empty' even though there are VMs in ON state with public/private IPs. Workaround Cloud Discovery: In the case of large number of member accounts, datacenters/regions and VMs, results in huge number of IPs to be discovered.

In order to improve the performance and reduce the time for VM IP Discovery Schedules, kindly follow the below steps:

In the Application Navigator , go to System Definition > Script Includes.

Search for the Name: CloudDiscoveryScheduleConfig, and open the record.

In the script field, go the function populateIPAddressList.

At the end of the "populateIPAddressList" function comment out or remove the below lines of code which ever is present

//Remove the duplicates

ipAddressList = ipAddressList.filter(function(ip, index){

return (ipAddressList.indexOf(ip) == index)

});

or

return new DiscoArrayUtil().unique(ipAddressList);

Update the script.

Go to DiscoveryCloudConfig - Line 174

Change from:

if (is_master_account || ((service_account_data.datacenter_type == 'cmdb_ci_google_datacenter') && service_account_data.organization_id))

To:

if ((service_account_data.datacenter_type == 'cmdb_ci_google_datacenter') && service_account_data.organization_id);