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

Wrong user used for services when using upstart #96

Closed
memelet opened this issue Dec 2, 2014 · 6 comments
Closed

Wrong user used for services when using upstart #96

memelet opened this issue Dec 2, 2014 · 6 comments
Assignees
Milestone

Comments

@memelet
Copy link

memelet commented Dec 2, 2014

When the init_style is runit no user is created. But then when any of resources are used (ie, consul_service_def) they try to use node['consul']'service_user'.

@johnbellone
Copy link
Contributor

@memelet Would you mind testing against master?

@memelet
Copy link
Author

memelet commented Jan 13, 2015

Sorry, kind of lost track here. I have been using init_style=init but with this recipe (using 0.6.0):

# This is to work around https://github.com/johnbellone/consul-cookbook/issues/96

user "consul service user: #{node['consul']['service_user']}" do
  username node[:consul][:service_user]
  home '/dev/null'
  shell '/bin/false'
  comment 'consul service user'
end

group "consul service group: #{node[:consul][:service_group]}" do
  group_name node[:consul][:service_group]
  members node[:consul][:service_user]
  append true
end

Next time I work on this wrapper I will test without creating the user.

@johnbellone johnbellone self-assigned this Feb 9, 2015
@johnbellone johnbellone added this to the Road to 1.0.0 milestone Feb 9, 2015
@dpkp
Copy link
Contributor

dpkp commented May 5, 2015

Fixed in 0.7.0?

@johnbellone
Copy link
Contributor

I'll wrap this up with the 1.0 release.

@johnbellone
Copy link
Contributor

I am closing this out because of impeding #126 landing on master.

@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

3 participants