-
Notifications
You must be signed in to change notification settings - Fork 22
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
409 Conflict - Error when creating hetznerdns_records #5
Comments
Thank you for reporting @atlan78. The information you provided was very helpful :-). I was able to reproduce and can confirm it's a bug. I'll look into it in the next couple of days. |
Can be reproduced with the following resources.
The first record is created, for the second the API returns a 422 Unprocessable Entity. When applied twice, everything works fine. |
Wow, you are fast. I'll test it soon. |
Turned out that the Hetzner API doesn't like creating more than one DNS record at a time. To be fair, there is a bulk create API endpoint which could be used to support this, but I decided to synchronize the API calls in code for now. This will slow down CRUD of DNS records. I hope there are not too many in your project. Release v1.0.4 fixes this issue. |
Works perfectly now. Now i can set all the 'A' and 'AAAA' records for all of my k8s-nodes.
Great Work! |
See Issue #5 for context. Serialized all requests to the API, but only PUT and POST requests cause the issue.
I have a terraform resource which should create a dns-record entry for each server I created before:
When applying this resource, the following error occurs:
Terraform will perform the following actions:
Output:
The error occurs, but the 2 records are created in Hetzner-dns:
Do I make a mistake while creating these resources or is there a bug? How can this error be avoided?
Debug-Output at Loglevel DEBUG:
The text was updated successfully, but these errors were encountered: