-
-
Notifications
You must be signed in to change notification settings - Fork 243
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
consul service user /bin/false shell ? #271
Comments
Which checks are failing? |
I mean consul_definition, type=check. In other words any script execution: parameters(script:'xyz.sh'). As the "service consul user" don't have a proper shell configured. I workaround it by:
Related, I test it with Vagrant + opscode-centos-7.1 image. |
Ah, interesting. It makes sense that this doesn't work just wonder why we never caught it before. |
This was fixed in recent patch. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I have testes 1.4 version from master and found the service_user created "consul" is being OOTB created with /bin/false default shell. Which causes all scripted checks effectively silent.
poise_service_user
doesn't have the "shell" attribute. So the only way to make the user with effective shell is to create him first. https://github.com/poise/poise-service#poise_service_userAs I am quite new with consul I am not about to post PR as this might be resolved multiple ways.
The text was updated successfully, but these errors were encountered: