-
Notifications
You must be signed in to change notification settings - Fork 1
Webhook tries to create record in wrong zone #33
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
Comments
Can you tell me what the record was, and what zones were available? I assume |
thats the point |
The interesting point is that the error is no persistent. At the next reconciliation the record get created in the right zone. |
I opened #37 to fix another issue I encountered with zone matching. I don't see how this issue would be fixed by it, though, especially since your error is not always occuring. I did add a test for your case, which was successful. |
The fix in #37 dont fix my issue. Today I upgraded to version 1.0.1 and i got
|
Hello,
we found a Bug that the provider tries to create a record in the wrong zone. We found the following Log line at OpenStack side:
"POST /v2/zones/93b315cf-c256-4ec8-bca9-4fafa73ffd14/recordsets HTTP/1.1\" status: 400 "}
The Webhook Provider make following Logs
The text was updated successfully, but these errors were encountered: