Closed gshively11 closed 9 years ago
I'm pretty sure this is a regressions... @manderson26 thoughts? -s
I also bumped into this on a CentOS 6.6 node using push-jobs cookbook v2.4.0
Fixed in cookbook version 2.4.1 using this commit: https://github.com/opscode-cookbooks/push-jobs/commit/7d6842526ff9786102f7349e64b4851eef6c969b
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?