-
Notifications
You must be signed in to change notification settings - Fork 782
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
With wait
consul-template never starts the program
#1043
Comments
Having the same issue with multiple templates and wait configured via command line flags. It works with just one template, though. |
I am experiencing the same problem. I have some more information. If there are multiple templates and the wait state applies to more than one then the program never starts. The failure applies to consul-template in long-running mode. In -once mode, the program does start. This works:
This works:
This FAILS:
This FAILS:
The common thread between those last two scenarios is that the wait states apply to more than one of the templates. Hope this helps! |
When consul-template -wait argument is given, the exec command is never executed. See hashicorp/consul-template#1043
I ran this down with I'll go out on a limb that @dadgar's refactor in #988 between 0.19.0 and 0.19.1 needs another set of eyes, as it resulted in bug #991 and fixing that caused this bug, and likely there's some deeper race condition. Hope this is enough information to debug to a resolution, I'm tapped out for the day in my timezone. |
We are bitten by this bug. |
@pearkes I've debugged this to the point of providing a reproduction case and a suspect commit. Are you able to take it from here to a fix given this information? |
Any update on this? |
I believe I have a fix in #1174. It is the best I could do with my understanding of the system, but does resolve this behavior and calls |
Consul Template version
0.19.4 (works with 0.19.0)
Configuration
Command
../consul-template \ --config=alertmanager.hcl \ --exec 'bash -c "echo start; sleep 10; echo stop"'
Debug output
0.19.4
0.19.0
Expected behavior
0.19.4 should behave like 0.19.0
Actual behavior
It never starts the command
The text was updated successfully, but these errors were encountered: