-
Notifications
You must be signed in to change notification settings - Fork 7
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
Puppet cannot load the jerakia-client gem #6
Comments
Hi @den-is Firstly, you are right, the Jerakia puppet module should include better docs on the pre-requisites for puppetserver like installing the jerakia-client gem, I'll get this into a new release. Your stack trace indicates that Puppet is failing because jerakia-client is not getting a successful response form the server (https://github.com/crayfishx/jerakia-client/blob/master/lib/jerakia/client.rb#L98) - note that you don't need to install lookup_http into Puppet's ruby - the client does Net::HTTP natively. I'm missing quite a lot of info here - can you also send your I suspect that maybe hiera.yaml is misconfigured... but it's hard to say without seeing the contents.... Craig |
hiera.yaml ---
version: 5
defaults:
hierarchy:
- name: jerakia
lookup_key: jerakia
options:
token: puppet:tokeeeen...0c08ea9cad3266df091d4c38a0c
scope:
env: "%{environment}"
- name: "Common"
paths:
- "common.yaml" jerakia.yaml ---
policydir: /etc/jerakia/policy.d
plugindir: /var/lib/jerakia/plugins
loglevel: debug
logfile: /var/log/jerakia/jerakia.log
databasedir: /var/db/jerakia policy policy :default do
lookup :couchdb do
datasource :http, {
:host => "10.0.2.2",
:port => 5984,
:output => "json",
:paths => [
"/config/#{scope[:env]}",
"/config/global",
"/config/app",
]
}
end
end By itself jerakia is working fine from CLI. |
It's not not sending back a known failure, probably a 500 judging by the line that raises the exception... can you test this from the command line against the API.....
(assuming that you're puppet environment is production) Can you see what that gives you? |
First of all: good to know such troubleshooting URL. I found issue, but actually it's not completely my issue.
As by policy it had to failover to After I've added
|
For others that may be looking into Jerakia, but hitting this error. See https://tickets.puppetlabs.com/browse/SERVER-571 for more background as to why the jerakia-client currently needs to be installed twice. Install jerakia-client gem for ruby (puppet apply) Install jerakia-client gem for jRuby (puppetserver) I was following https://www.craigdunn.org/2017/04/managing-puppet-secrets-with-jerakia-and-vault/ and http://jerakia.io/integration/puppet System details
|
Need help,
Can't find what am I missing.
This is completely development fresh setup for experimentation purposes.
After installing following all instructions from official jerakia site I'm still getting this error:
I wasn't able to find obvious instruction about installing
jerakia-client
next error
and puppetserver.log
https://pastebin.com/gnG9DjAD
trying this:
But getting same error from above.
Dummy module for tests:
site.pp
All above is just working without jerakia.
Jerakia is working fine by itself
The text was updated successfully, but these errors were encountered: