After Upgrading to Washington I get an error when refreshing datacenters for Azure Cloud Discovery

[Traian Stefan 1]

After I Upgraded the instance to Washington when I create Schedules from Cloud Discovery Workspace at the step of refreshing datacenters I get this error: ' CI Type cmdb_ci_azure_datacenter cannot be created since there are no attributes defined. Debug pattern to understand why no attributes have been assigned.'

The implementation was successful before the Clone and I had no issue in getting the datacenters and 100% of the data from Azure.

To be mentioned that I implemented Credential-based and the implementation is correct.

Even Servicenow personnel it's puzzled because I didn't used to get this error and here is the funny part: 

I have 15 Schedules left that got this error, however there used to be 18.

After I updated to the latest version for Discovery and Service Mapping patterns 2 schedules started working without this error and refreshed the datacenters.

After I migrated from Probes to Patterns 1 more schedule didn't receive the error anymore.

Issue 1. Half the accounts have this error: 'Identification sections in pattern failed: section: Azure Datacenter identification, error: Match step predicate is not matched. Failed Condition(s): [(${locations_rest_resp} : value=) IS ' meaning there are no datacenters in that account to return (which is false).

Issue 2. The other accounts have this error: ' CI Type cmdb_ci_azure_datacenter cannot be created since there are no attributes defined. Debug pattern to understand why no attributes have been assigned.'

Can you please help me in understanding why it doesn't refresh datacenters ? 

To mention that I tried from the Service Account form also and I get an error.

Thank you.

[Pankaj Godselaw]

Hi Traian,

Did you find any solution to this error? We are facing similar errors during Azure discovery. Were you able to solve it?

[amar7]

Hi pankaj,
did you find the solution to this we are facing the similar issue in Azure discovery while Creating a schedule. 

[amar7]

Hi Traian,

did you find the solution to this we are facing the similar issue in Azure discovery while Creating a schedule.