All Errors

The ClusterAlreadyExists error occurs when Terraform attempts to create a Redshift cluster with an identifier that already exists in your AWS account. Since cluster identifiers must be unique within an account and region, this error indicates the cluster was previously created or still exists from a failed operation.

This error occurs when trying to create an Azure Key Vault with a name that already exists, either as an active vault or in a soft-deleted state. Azure Key Vaults have globally unique names and are subject to soft-delete retention periods.

AWS WAF has account-level quotas on the number of WebACLs, rules, and other resources you can create. This error occurs when you exceed those limits. Resolve it by consolidating resources, removing unused WAF entities, or requesting quota increases.

Terraform's TLS certificate parsing error occurs when the TLS provider encounters malformed, expired, or untrusted certificates. This error typically appears when using data sources like tls_certificate or connecting to remote backends with problematic certificates.

Helm deployments often timeout when Kubernetes resources take longer than expected to reach their desired state. This error typically indicates insufficient cluster resources, slow image pulls, or misconfigured healthchecks that prevent pods from becoming ready.

This error occurs when Terraform cannot parse a timestamp string in RFC3339 format, commonly from AWS SSO credentials or invalid time provider usage. Fixing it involves updating credentials, correcting timestamp formats, or using the time provider correctly.

State migration fails when Terraform cannot automatically transfer state from an old backend to a new one. This typically occurs due to version mismatches, lock conflicts, permissions issues, or backend connectivity problems during terraform init -migrate-state.

Terragrunt shows this error when it cannot determine the specific exit code from an underlying command failure. The actual error is usually displayed before this message, making it crucial to look at the full error output to identify the root cause.

This warning appears when SSH detects that a remote server's host key has changed since you last connected to it. The offending key is stored in your known_hosts file, and SSH refuses to connect until you remove or update the old key entry.

A Terraform provisioner (local-exec or remote-exec) executed a command that failed with exit status 1. This occurs when the underlying script or command returns a non-zero exit code, causing the provisioner to fail and mark the resource as tainted.

This error occurs when Terraform attempts to create a Kubernetes ConfigMap that already exists in the cluster. Common with aws-auth ConfigMaps in EKS or when re-applying configurations. Resolving it requires either importing the existing resource into Terraform state or removing the existing ConfigMap first.

Terraform cannot find a file specified in your configuration using the `file()` function or `local_file` data source. This usually happens due to incorrect file paths, timing issues with resource creation, or module dependency problems.

The "secrets already exists" error occurs when Terraform attempts to create a Kubernetes Secret that already exists in the cluster. This can be resolved by importing the existing secret into Terraform state, using kubectl apply instead of create, or handling the 409 Conflict error in your workflows.

This error occurs when Terraform attempts to create a GCP Service Account that already exists in your project. The fix involves either using the create_ignore_already_exists flag or importing the existing account into your Terraform state.

This error occurs when a Terraform provisioner (local-exec, remote-exec, or file) tries to execute a command that doesn't exist in the target environment's PATH. This typically happens when commands are called by name rather than full path, or when dependencies aren't available in Terraform Cloud environments.

This error occurs when Terraform fails to create a GCP Cloud SQL instance due to state conflicts, permission issues, or timeout problems. The operation failed because another operation was in progress, the instance name was recently deleted, or required APIs were not enabled.

This error occurs when Terraform or kubectl attempts to create a Kubernetes Deployment while the target namespace is in a Terminating state. The namespace is stuck in the process of being deleted, preventing new resources from being created.

The Terraform archive_file data source cannot find the source file or directory specified in your configuration. This happens when the path is incorrect, uses the wrong base directory, or references a file that does not exist at plan time.

Terraform failed because an external program exited with a non-zero status code. This commonly occurs with data sources, provisioners, or custom scripts that encounter errors during execution.

GCP Cloud Functions deployment fails with a generic DeploymentError when using Terraform. This typically occurs due to missing API enablement, IAM permission issues, source code configuration problems, or build service account misconfiguration.