Skip to content
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

Retry reading DNS zone and Compute instance state after creation #1303

Merged
merged 1 commit into from Nov 4, 2021

Conversation

pbasov
Copy link
Contributor

@pbasov pbasov commented Oct 25, 2021

We had some issues with our cloud which buckled under a high load, which resulted in a bunch of 504 errors.

Provider didn't handle the errors during async operations with DNS zones and Compute instances, which resulted in mismatched states when cloud resources were actually created, but didn't go into ACTIVE state before an intermittent API error.

This change let's the provider keep refreshing the state through 502 and 504 errors, to prevent missing resources in state, that are already present on the cloud.

  * Prevents state mismatch in case of server errors
@pbasov pbasov changed the title Retry reading DNS zone state after creation Retry reading DNS zone and Compute instance state after creation Oct 25, 2021
@theopenlab-ci
Copy link

theopenlab-ci bot commented Oct 26, 2021

@pbasov
Copy link
Contributor Author

pbasov commented Oct 26, 2021

recheck

@theopenlab-ci
Copy link

theopenlab-ci bot commented Oct 26, 2021

@pbasov
Copy link
Contributor Author

pbasov commented Oct 29, 2021

recheck

@theopenlab-ci
Copy link

theopenlab-ci bot commented Oct 29, 2021

@ozerovandrei
Copy link
Member

Networking errors in tests are unrelated to changes in this PR.

Copy link
Member

@ozerovandrei ozerovandrei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ozerovandrei ozerovandrei merged commit 74b6c76 into terraform-provider-openstack:main Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants