Troubleshooting SIC-001 Error: Failed to Retrieve Configuration in Terraform Cloud

Issue: Users encounter the error SIC-001: Failed to ingress entity: operation failed: failed to fetch refs: failed on ls-remote: repository not found: Repository not found when running Terraform Cloud workspaces integrated with a Version Control System (VCS). This issue prevents Terraform Cloud from retrieving configuration from the repository, leading to failed runs.

• Terraform Cloud fails to retrieve configuration from VC.

• Runs fail with the following error message:

• Error: failed to retrieve configuration
  Retrieving the configuration version failed with the error: Internal error: SIC-001.
  Failed to ingress entity: operation failed: failed to fetch refs: failed on ls-remote: repository not found: Repository not found.

• Other workspaces in the same organization may function normally.

Possible Causes:

1. Deleted or Disconnected VCS Account:

   • If the VCS account linked to the workspace has been deleted or access revoked, Terraform Cloud cannot retrieve the configuration.

2. VCS Repository Moved or Deleted:

   • The repository linked to the workspace may have been deleted, moved, or renamed.

3. VCS Service Outage:

   • Temporary outages in VCS providers (e.g., GitHub, GitLab) may prevent Terraform Cloud from fetching configuration.

4. Incorrect Repository Access Permissions:

   • The linked VCS account may no longer have the required permissions to access the repository.

5. Misconfigured Workspace VCS Settings:

   • The workspace may be pointing to an incorrect or non-existent repository.

Resolution Steps:

Step 1: Verify the VCS Connection

• Navigate to Terraform Cloud > Workspaces > (workspace-name) > Settings > Version Control.

• Check if the repository is accessible and correctly linked.

• If the repository is missing or incorrect, update it with the correct repository.

Step 2: Re-authenticate VCS Connection

• If the linked VCS account has been changed, reconnect it:

  1. Go to Terraform Cloud > Settings > VCS Providers

  2. Select the correct VCS provider and reauthorize the connection.

  3. Re-link the affected workspace to the correct repository.

Step 3: Push a No-Op Commit

• If the repository and credentials are correct, try triggering a new run by pushing a blank commit

Step 4: Check VCS Provider Status

• Verify if there were any recent outages with your VCS provider (GitHub, GitLab, etc.).

• Check GitHub Status at https://www.githubstatus.com/

Step 5: Perform a Manual Run

• If the issue persists, manually trigger a Terraform plan from the UI:

  • Terraform Cloud > Workspaces > (workspace-name) > Runs > Start a new run