-
Notifications
You must be signed in to change notification settings - Fork 29
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
Provider intermittently fails to initiate MikroTik API #39
Comments
Hey @peteleblond, thanks for the report. I upgraded my terraform version to v1.0.1, but I haven't been able to reproduce it. It appears that this script code is not handling errors before running a command (here and here) :( Are you able to compile the provider yourself? If so, please apply this diff with
If that will be difficult then we can get that change merged into master, create a new release and have you try it again. This code also creates a new connection for each function called, which is inefficient and I believe is leaking sockets. How many resources are in this terraform configuration? |
Hi @ddelnano Thanks for checking this out. Great work with this Provider, it's going to be immensely useful! Currently, there are only 2 resources in my TF config, one of each type I'm afraid I'm not sure how to compile this myself, though I'll try and look it up when I get a chance. If you could get the change merged into master I'll test again as soon as I can. |
I have that change included in v0.6.2. Please install v0.6.2 (it should be pushed to the terraform registry in the next hour or so), reproduce the problem and attach your logs again and hopefully we will have a better clue 🤞 |
Sorry, I might have the wrong end of the stick here, but v0.6.2 doesn't seem to be in the TF registry yet, is that expected? I was having a play with Am I missing something? |
Sorry, it is now. I forgot to publish the release on github, which is why it was hidden. |
@peteleblond would appreciate if you get a chance to try out the latest release. |
Using provider version 0.6.0 and Terraform 1.0.0 & 1.0.1 it appears that the provider intermittently fails to initiate MikroTik API when running (and re-running) a
terraform plan
orterraform apply
. This appears to happen intermittently even if the code remains totally unchanged. Usingtcpdump
, I've confirmed that API traffic can be seen when the terraform operation suceeds, but there is no API connection attempt when the this problem is encountered.Example error message (for
terraform plan
):Other relevant info:
In my configuration, Terraform is only configured to manage MirktoTik resources
mikrotik_script
andmikrotik_scheduler
.Provider config:
The text was updated successfully, but these errors were encountered: