Troubleshooting Looker (Google Cloud core) instance creation failures

This guide helps you troubleshoot failures during the creation of Looker (Google Cloud core) instances.

The troubleshooting process is broken down into two trees based on symptoms:

Symptom: Instance creation failure

If you're encountering a failure while trying to create a Looker (Google Cloud core) instance, use the following decision tree to begin troubleshooting. This tree helps route you to setup guides for first-time deployments, to Sales for discontinued editions or Quota increases, to network configuration steps for a Shared VPC, or to specific bug mitigations for intermittent Filestore errors.

Troubleshooting steps:

  1. First-time creation? If yes, review the setup guide to ensure that all steps were followed.
  2. Quota Issue? If you suspect a Quota issue, contact your Sales or Account Executive.
  3. Trial/Monthly Standard? If you're using an expired or discontinued edition, refer to current Looker pricing.
  4. None of the above? Proceed to the Network Validation Failures tree.

Symptom: Network validation failures

If you're encountering network validation failures, such as RANGES_NOT_RESERVED or RANGES_EXHAUSTED, use the following decision tree to troubleshoot. This tree helps identify specific range reservation errors and verify if a Shared VPC is in use. You may be guided to reserve IP ranges, expand existing allocations, or perform manual Looker service account setup steps for Shared VPC environments.

Troubleshooting steps:

  1. RANGES_NOT_RESERVED? Reserve the necessary IP ranges for your instance.
  2. RANGES_EXHAUSTED? Expand the existing IP range allocation.
  3. Shared VPC? If you're using a Shared VPC, ensure that the Looker service account is enabled and has the compute.globalAddresses.get permission.
  4. None of the above? Contact Support if you need further assistance.