-
Notifications
You must be signed in to change notification settings - Fork 77
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
Occasional error updating SSL endpoint #180
Comments
Does this seem like another use case for adding a delay, similar to #158? |
Yes, a wait that continues waiting under these error conditions would be the fix, but waiting after the platform returns errors seems like a bad idea because it should fail when errors are encountered. Fortunately I believe the underlying platform issue was fixed last week. These errors have not appeared in almost a week. Continuing to observe and will close this issue once the certain of the fix. |
Awesome. If not let me know, I can work on a fix. I finally have some breathing room back 😰 |
It's been a week since we've seen this error in daily CI runs, so closing since it seems to be fixed by Heroku! |
Since getting CI running, I've observed that one of our flakey tests is for the SSL certificate
heroku_cert
resource.Terraform Version
Affects
Terraform v0.11.x
versions too.Affected Resources
heroku_addon
,plan = "ssl:endpoint"
heroku_cert
The cert explicitly depends on the addon's state.
Terraform Configuration Files
From the test file:
Debug Output
Flakey test failures, like this one when running on my local machine:
In TeamCity CI they look like this:
And sometimes the errors are a
503
status:Expected Behavior
The SSL certificate
heroku_cert
should be uploaded successfully to the SSL endpointheroku_addon
.Actual Behavior
Sometimes it fails, throwing this "try again later" message.
Steps to Reproduce
Set yourself up for testing
Run this test over & over again, eventually it will fail:
Important Factoids
Perhaps the certificate resource should be patient with SSL endpoint 😇
The text was updated successfully, but these errors were encountered: