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.

Sign up for GitHub

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

Jump to bottom

Change in client_key path in v2.4.0 #38

Closed
gshively11 opened this issue Jul 22, 2015 · 3 comments
Closed

Change in client_key path in v2.4.0 #38

gshively11 opened this issue Jul 22, 2015 · 3 comments

Comments

@gshively11
Copy link

In the latest release, this line was added, which now forces the push jobs client to look for the client key in /etc/chef/secure. However, my client key has always been stored in /etc/chef, and previous versions of the push job client have worked. This prevents the push jobs service from starting.

I wouldn't expect a breaking change like this in a 2.x.0 bump, but maybe my stuff is not configured according to standards. Can you add some clarification to this change please?
@someara
Copy link
Contributor

someara commented Jul 22, 2015

I'm pretty sure this is a regressions... @manderson26 thoughts?
-s

@Roviluca Roviluca mentioned this issue Jul 28, 2015
Closed
@alexpop
Copy link
Contributor

alexpop commented Jul 28, 2015

I also bumped into this on a CentOS 6.6 node using push-jobs cookbook v2.4.0

@markan markan added the bug label Jul 28, 2015
@alexpop alexpop mentioned this issue Jul 29, 2015
Closed
@alexpop
Copy link
Contributor

alexpop commented Jul 30, 2015

Fixed in cookbook version 2.4.1 using this commit: 7d68425

@alexpop alexpop closed this as completed Jul 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@someara @alexpop @markan @gshively11