SyncWorkspace pod reporting workspace as errored even though it's not

[EmmanuelOgiji]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

terraform-k8s & Kubernetes Version

terraform-k8s version: 1.1.0
Kubernetes version 1.22

Affected Resource(s)

Terraform cloud operator sync workspace pod is reporting that a workspace run could not be completed and the workspace has errored even though that is not the case.

This is part of migrating state to Terraform Cloud and although the initial run failed, a few terraform state commands and UI re-runs later, the workspace applied successfully. However, the sync workspace pod references the latest runID i.e. the successful run for still reports its status as errored.

Deleted the pod and allowed the deployment/replicaset to recreate to see if that would help but it didn't

Debug Output

Log Output: https://gist.github.com/EmmanuelOgiji/864091c75f6bc746b1dea7f862d376f5

Expected Behavior

The operator pod should have reconciled and reported that the workspace is in fact now applied.

Actual Behavior

It still reports as errored

Steps to Reproduce

• Migrate state from S3 to Terraform cloud
• Perform terraform state mv commands (as using the CRD means everything goes under 'module.operator' in state when using the CRD)
• Trigger a run via Terraform Cloud UI
• Run kubectl -n $NAMESPACE describe workspace $WORKSPACE name

[EmmanuelOgiji]

Seems like this is the same issue as #143. I resolved by triggering a "dummy" run via the operator i.e. change a variable but that is only a workaround