Google Cloud Platform patterns fails due to missing logical datacenters in the pattern library Google GCP - Get Logical DatacenterDescriptionGoogle Cloud Platform patterns fails due to missing logical datacenters in the pattern library "Google GCP - Get Logical Datacenter". When GCP discovery is scheduled against all regions, a few patterns like "Google Cloud Platform (GCP) - Virtual Server" , "Google Cloud Platform (GCP) – Storage" and "Google Cloud Platform (GCP) - Disk Types" fails. However, when GCP discovery is scheduled only for a single region like US East1 region, only Google Cloud Platform (GCP) – Storage pattern fails, or possibly no patterns fail. Errors like following example can be seen in the pattern log: Identifier: Identification CI Errors:In payload no relations defined for dependent class [cmdb_ci_disk_type] that matches any containment/hosting rules: [cmdb_ci_disk_type >> Hosted on >> cmdb_ci_logical_datacenter]. Add appropriate relations in payload for '{"className":"cmdb_ci_disk_type","values": This may happen when pattern library "Google GCP - Get Logical Datacenter" is not out of box. To confirm if this is the root cause (the outdated library), open the pattern library and ensure that it is using the most recent OOB version. In the example above we see the current version being used has the most recent "Recorded at" date and source "Store Application: Discovery and Service Mapping Patterns". This means it is using the most recent OOB version. If no versions are listed, this would also confirm it is using the most recent OOB version as versions are usually only listed when the records is modified from OOB.Steps to Reproduce Run GCP discovery for all regions Confirm errors Run GCP for single region US East1 region and observer a lower number of patterns failedWorkaroundRevert to the most recent version of the pattern library "Google GCP - Get Logical Datacenter".Related Problem: PRB1505324