-
Notifications
You must be signed in to change notification settings - Fork 277
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
Droplet already has a pending event for reserved_ip #1034
Comments
Hi there, thank you for the write up! Hmmm....I can't seem to recreate this issue on my end. Are there any more details you can provide about the config you're using or if you have to run it multiple times to see the issue? For reference, this is the config file I'm using:
|
It will probably be difficult to reproduce, but happens for me quite consistently. Try to apply the infrastructure once and then do a small change (in user data, for example) and apply again. I have this now:
Even with this setup, I often get the same error. It is probably some kind of synchronization issue on the API side when reserved ip is being assigned to the droplet. |
Bug Report
Describe the bug
Having
Applying often causes
Droplet already has a pending event
error, failing deployment.Restart of the deployment results in
Error: Error retrieving reserved IP: stream error: stream ID 17; INTERNAL_ERROR; received from peer
Affected Resource(s)
digitalocean_reserved_ip
Expected Behavior
Actual Behavior
Steps to Reproduce
Terraform Configuration Files
Terraform version
Debug Output
Panic Output
Additional context
Important Factoids
References
The text was updated successfully, but these errors were encountered: