-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws:batch:JobDefinition Resource provider reported that the resource did not exist while updating #3845
Comments
@jamie1911 thanks for reporting this issue. We'll need to do some research on this to figure out a root cause. |
I have found the issue here. #3792 increased the provider to https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.44.0 which has a new parameter Which doesn't seem to be working or should be documented correctly or defaulted to the previous behavior. Any advice? |
@jamie1911 it looks like this issue is being tracked upstream by hashicorp/terraform-provider-aws#36824. The issue is marked |
Thanks, I am personally okay waiting for an upstream fix, I have reverted our process to pin to |
The fix was just released in the latest version of Terraform, so this should be fixed in our next release. |
Unfortunately inheriting the fix has opened up another regression over BatchDefinition. I believe we have a fix here: #3888 which will be releasing shortly. Appreciate your patience. |
This should be fixed in the latest release. Please et us know if there are any remaining problems in this area. |
Cannot close issue:
Please fix these problems and try again. |
What happened?
It seems something has changed and now Job Definitions for AWS batch seem to be getting in a strange state.
We get errors like:
However, the Job Definitions do exist. What actually ends up happening is now there are duplicate job definitions with multiple revisions. Previously, it would unregister the old job definition and create a new revision.
Example
Output of
pulumi about
Additional context
It seems either retrying the GitLab job will run successfully. Or it will run successfully if we first run refresh then retrying the job. However, any job after will work 1 time then will fail until the steps are repeated.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: