-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Bug]: elastic beanstalk environment update failed #32284
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Hey @Omerlustig 👋 Thank you for taking the time to raise this! So that we have the necessary information in order to reproduce this, can you supply a sample Terraform configuration that can be used to reproduce this bug, as well as debug logs (redacted as needed)? |
any updates? do you need more details? |
Hey @Omerlustig 👋 Thank you for checking in on this! Unfortunately I can't provide an ETA on when this will be looked into due to the potential of shifting priorities. We prioritize by count of 👍 reactions and a few other things (more information on our prioritization guide if you're interested). Based on a quick look, I don't believe that there's any additional details that we need at this time, but once this gets prioritized, whoever is working on it may ask for additional information based on what they find. |
Hi @Omerlustig did you figure out a workaround to be able to deploy when this issue happen ? |
This functionality has been released in v5.40.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.5.1
AWS Provider Version
5.5.0
Affected Resource(s)
when updating beanstalk environment getting this error:
started happening after upgrading to provider version 5.5.0 from 4.62.0
Expected Behavior
update should finish successfully.
Actual Behavior
beanstalk update fail.
Error: updating Elastic Beanstalk Environment (e-2brbmjtpwk): InvalidParameterValue: Environment named neo-web-app-devops is in an invalid state for this operation. Must be Ready.
Relevant Error/Panic Output Snippet
Details:
the error starts happening from 4.63.0 version of the proivder (did not happen in 4.62.0). and keeps happening even when using latest version.
it happens when beanstalk environment tags are changed. so probably it might be related to that.
when deploying the beanstalk environment without changing any tags it works fine but once a tag is changed it fails with the error that the environment is not ready
Terraform Configuration Files
Steps to Reproduce
update elastic beanstalk environment with terraform version 1.5.1 and aws provider version 5.5.0
Debug Output
4.62.0 works good
issue started at 4.63.0
might be related to tags that are being chaged (didnt happen in version 4.62.0)
Failure - plan output
Success - plan output
The text was updated successfully, but these errors were encountered: