All Errors

The "No Space Left on Device" error occurs when Terraform runs out of disk space during initialization, planning, or apply operations. This typically happens in CI/CD environments or when provider caches grow too large. Diagnose disk usage and implement caching strategies to resolve.

Terraform import fails when credentials aren't configured locally. Unlike other Terraform commands that run in the cloud, terraform import executes on your workstation and requires local authentication to access cloud resources.

This error occurs when Terraform tries to create a GCP resource (like Dataflow jobs) but the required API hasn't been enabled in your Google Cloud project. The fix is to explicitly enable the API using the google_project_service resource in Terraform or via gcloud CLI.

This error occurs when Terraform's Azure provider fails to authenticate with the Resource Manager API. It typically happens due to missing Azure CLI, authentication issues, or configuration problems with OIDC or service principal credentials.

When using Terraform with Google Cloud Platform, you may encounter a 409 error stating 'The resource already exists' when trying to create or update SSL certificates. This typically occurs when the certificate wasn't properly deleted after a previous operation, or when using create_before_destroy lifecycle rules with managed certificates.

This error occurs when the Terraform Azure provider attempts to use an API version that doesn't exist or isn't registered in your subscription. It typically indicates either resource provider registration issues, API version mismatch, or regional API support limitations.

The Cloud Resource Manager API disabled error occurs when Terraform tries to manage GCP resources but the cloudresourcemanager.googleapis.com API has not been enabled on the project. This is a chicken-and-egg problem where the API must be manually enabled before Terraform can use it.

The "InUseRouteTableCannotBeDeleted" error occurs when Terraform tries to delete an Azure route table that is still associated with a subnet. Azure prevents deletion of route tables that are actively in use, requiring proper disassociation before removal.

The "Invalid for_each argument" error occurs when Terraform cannot determine the keys in a for_each loop before applying the plan. This typically happens when the for_each value depends on computed resources or unknown attributes that haven't been created yet.

The ResourceDependencyException error occurs when Terraform tries to delete AWS Image Builder Components or Recipes that have dependent resources (like Image Pipelines) still referencing them. Terraform attempts to delete resources in the wrong order, causing AWS to reject the deletion. You must manually manage the deletion order or use workarounds.

Terraform's .terraform.lock.hcl file records provider package checksums to ensure security and consistency across different systems. A checksum mismatch occurs when the provider binary being installed doesn't match the recorded checksum, typically due to platform differences or provider version changes.

The Terraform operation was terminated by the system, usually due to memory exhaustion or timeout. This occurs when the process consumes more resources than available, commonly with large state files or high-concurrency operations.

This error occurs when apt cannot establish a connection to a configured proxy server. Common causes include incorrect proxy configuration, unreachable proxy server, wrong credentials, or firewall blocking.

The "Cannot set to hold" error occurs when attempting to hold an uninstalled package using apt-mark. This is intentional behavior by dpkg—held status only works on installed packages. Uninstalled packages can be locked from installation using APT preferences instead.

The dpkg package manager encountered a corrupted .list file in /var/lib/dpkg/info/ that contains an empty filename. This prevents apt from functioning and requires manual repair of the corrupted package metadata.

The "no installation candidate" error for i386 packages occurs when apt cannot find a suitable version of a 32-bit package due to multiarch not being enabled, missing repositories, or version conflicts. Enable i386 support and update your package cache to resolve this.

The "invalid for APT::Default-Release" error occurs when the release name specified in your APT configuration doesn't match any release in your sources.list. This prevents apt from finding the specified distribution, causing package installation to fail.

The "dpkg: error: unable to create new file: Permission denied" error occurs when your user account lacks sufficient permissions to modify package management directories. This is almost always resolved by running the command with sudo privileges.

The dpkg error code (2) typically occurs when the package manager encounters file system or permission issues, corrupt package lists, or incomplete installations. This can usually be fixed by reconfiguring dpkg, fixing broken dependencies, or removing lock files.

The "dpkg-divert: error: rename involves overwriting" error occurs when dpkg-divert tries to rename a file during package operations but finds a different file in the target location. This typically happens due to package conflicts, leftover files from failed installations, or incorrect diversion configurations.