-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Hitting authentication errors when running octodns sync for multiple new zones on the same run #108
Comments
What version are you running. The line numbers in your stack track e.g. 920, don't align with the current release 0.0.7 as that line isn't even in the Some sort of creation timing issue is a good guess, other possibility would be a rate limit of some sort. You might try throwing
--debug if you can reliably recreate the problem.
When I get a change to sit down and mess with it I'll try and reproduce the issue, but it sounds like it might be a tough one to do and may even rely on latency to CF's api servers etc. |
Yeah i was running 0.0.6. I'll try to run with extra debugging once we get the next bigger batch of zones to process through octodns! Thanks for the info! |
One extra tidbit of information: We intially worked around this issue by just running |
That does make it sound more like a rate limit than race condition, but 🤷
OK. Since it sounds like you have an account contact you might check with them and see if they have anything to say about eventually consistent creates/race conditions. |
So far no luck recreating this. I put together a test data source that creates 64 zones each with a single record and then tries to sync them. Eventhing works fine up to the point it hit the rate limit:
Going to rework things to create more records in each zone to see if that makes a difference, but otherwise this one is probably going to sit until it times out if we can't come up with reliable steps to reproduce. |
Actually looks like the rate limit (for me anyway) never recovers:
|
So we are creating new zones with DNS records in Cloudflare using octodns, and almost every time if there are enough new zones, we hit a
octodns_cloudflare.CloudflareAuthenticationError: Authentication error
at some point of the process. Usually before the 40th or so zone in the set.My gut feeling is that this is because octodns tries to create the records into the newly created zone too soon after creation, and Cloudflare throws back a 403. But I have a hard time verifying this, as this happens so sporadically.
Here's the full stacktrace for reference:
We can work around this by just rerunning the sync until all the zones are successfully processed, but this is a bit of a nuisance.
The text was updated successfully, but these errors were encountered: