Skip to content
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

Closed
epcim opened this issue Feb 2, 2016 · 5 comments
Closed

consul service user /bin/false shell ? #271

epcim opened this issue Feb 2, 2016 · 5 comments

Comments

@epcim
Copy link

epcim commented Feb 2, 2016

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_user

As I am quite new with consul I am not about to post PR as this might be resolved multiple ways.

@johnbellone
Copy link
Contributor

Which checks are failing?

@epcim
Copy link
Author

epcim commented Feb 3, 2016

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:

# change the user shell "so it may run scripts for checks"
user node['consul']['service_user'] do
  shell '/bin/bash'
  action :modify
end

Related, I test it with Vagrant + opscode-centos-7.1 image.

@johnbellone
Copy link
Contributor

Ah, interesting. It makes sense that this doesn't work just wonder why we never caught it before.

@johnbellone johnbellone added the bug label Feb 5, 2016
@johnbellone
Copy link
Contributor

This was fixed in recent patch.

@lock
Copy link

lock bot commented Apr 25, 2020

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.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants