-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Open
Labels
provisionersArea: ProvisionersArea: ProvisionersregressionSomething that used to work but no longer worksSomething that used to work but no longer workss2Broken use cases or features (with a workaround). Only humans may set this.Broken use cases or features (with a workaround). Only humans may set this.
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
Hi 👋,
We upgrade from v2.25 to v2.27, now we're running into this issue when a pod fails to be created initially and we want to retry:
Error: Unexpected Identity Change: During the read operation, the Terraform Provider unexpectedly returned a different identity then the previously stored one.
originates here:
hashicorp/terraform-provider-kubernetes#2779
v2.26.0 upgrades to terraform v1.13.0
unfortunately we can't roll back due to DB migrations (fails to start)
Thank you!
Relevant Log Output
Expected Behavior
No response
Steps to Reproduce
- create pod that fails
- retry
Environment
- Host OS:
- Coder version:
Additional Context
No response
Metadata
Metadata
Assignees
Labels
provisionersArea: ProvisionersArea: ProvisionersregressionSomething that used to work but no longer worksSomething that used to work but no longer workss2Broken use cases or features (with a workaround). Only humans may set this.Broken use cases or features (with a workaround). Only humans may set this.