Troubleshooting environment creation

This page provides troubleshooting information for problems that you might encounter while creating Cloud Composer environments.

For troubleshooting information related to updating and upgrading environments, see Troubleshooting environment updates and upgrades.

When Cloud Composer environments are created, the majority of issues happen because of the following reasons:

  • Service account permission problems

  • Incorrent Firewall, DNS or routing information

  • Network-related issues. For example, invalid VPC configuration, IP address conflicts, or network IP ranges that are too narrow

  • Quota-related issues

  • Incompatible Organiational Policies

Insufficient permissions to create an environment

If Cloud Composer cannot create an environment because your account has insufficient permissions, it outputs the following error messages:

ERROR: (gcloud.composer.environments.create) PERMISSION_DENIED: The caller
does not have permission


ERROR: (gcloud.composer.environments.create) PERMISSION_DENIED: User not
authorized to act as service account <service-account-name>.
The user must be granted iam.serviceAccounts.actAs permission, included in
Owner, Editor, Service Account User role. See
/understanding-service-accounts for additional details.

Solution: Assign roles to both to your account and to the service account of your environment as described in Access control.

The service account of the environment has insufficient permissions

When creating a Cloud Composer environment, you specify a service account that runs the environment's GKE nodes. If this service account does not have enough permissions for the requested operation, Cloud Composer outputs the following error:

Errors in: [Web server]; Error messages:
  Creation of airflow web server version failed. This may be an intermittent
  issue of the App Engine service. You may retry the operation later.
Message":"Your deployment has failed to become healthy in the allotted time
and therefore was rolled back. If you believe this was an error, try adjusting
the 'app_start_timeout_sec' setting in the 'readiness_check' section."}

Solution: Assign roles to both to your account and to the service account of your environment as described in Access control.

A VPC network selected for the environment does not exist

You can specify a VPC network and a subnet for your Cloud Composer environment when you create it. If you do not specify a VPC network, then the Cloud Composer service selects the default VPC and the default subnet for the environment's region and zone.

If the specified VPC network and subnet do not exist, then Cloud Composer outputs the following error:

Errors in: [GKE cluster]; Error messages:
        roject \"<your composer project>\" has no network named \"non-existing-
        v1/projects/<your composer

Solution: Before creating an environment, make sure that the VPC network and the subnet for your new environment exist.

Quota issues encountered when creating environments in large-scale networks

When creating Cloud Composer environments in large-scale networks, you might encounter the following quota limitations:

  • The maximum number of VPC peerings per single VPC network is reached.
  • The maximum number of primary and secondary subnet IP ranges is reached.
  • The maximum number of forwarding rules in the peering group for Internal TCP/UDP Load Balancing is reached.

Solution: Apply the approach recommended for Cloud Composer in large-scale networks.

Incompatible organizational policies

The following policies must be configured appropriately so that Cloud Composer environments can be created successfully.

Organizational Policy Cloud Composer 1 Cloud Composer 2
compute.disableSerialPortLogging Disabled for versions earlier than 1.13.0; otherwise any value Must be disabled
compute.requireOsLogin Must be disabled Must be disabled
compute.vmCanIpForward Must be allowed (required for Cloud Composer-owned GKE clusters) when VPC native mode (using alias IP) is not configured Any value is allowed
compute.vmExternalIpAccess Must be allowed for Public IP environments Must be allowed for Public IP environments
compute.requireShieldedVm Must be set to False Any value is allowed

For more information, see the Composer Known Issues page and Organization policy constraints.

400 Error Messages: Failed to deploy the Airflow web server.

This error might be caused by a failure to create a Private IP environment's GKE cluster because of overlapping IP ranges.

Solution: Check logs for any failures in your environment's cluster and resolve the issue based on the GKE error message.

What's next