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

vault entries are retrieved via puppet apply but not puppet agent #25

Open
drdam02 opened this issue Aug 19, 2016 · 3 comments
Open

vault entries are retrieved via puppet apply but not puppet agent #25

drdam02 opened this issue Aug 19, 2016 · 3 comments

Comments

@drdam02
Copy link

drdam02 commented Aug 19, 2016

I installed this backend and configured it according to the docs.

When running puppet apply -e "notice(hiera('its))" I get a correct response

Notice: Scope(Class[main]): atrap
Notice: Compiled catalog for server.domain.be in environment production in 0.47 seconds
Notice: Applied catalog in 0.09 seconds

but when running the same hiera parameter in a manifest like this

$hieratest = hiera('its',"nothing")
notify { "${hieratest}": }

I get this result

Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for lnx-iapuppet01.iconos.be
Info: Applying configuration version '1471610452'
Notice: nothing
Notice: /Stage[main]/Main/Node[server.domain.be]/Notify[nothing]/message: defined 'message' as 'nothing'
Notice: Applied catalog in 7.74 seconds

Puppetserver can't seem to find the its vault item, but puppet apply can

@jsok
Copy link
Owner

jsok commented Aug 19, 2016

Can you turn up the verbosity on puppet using --verbose --debug so hiera emits the debug level logs too?

@velocity303
Copy link

I had this same issue, but it was resolved when I made sure that vault-ruby was downgraded to the minimum version supported which was 0.4 instead of the latest version 0.7.3. After doing this, it worked like a charm with both puppet apply and puppet agent on Puppet Enterprise 2016.5. Not sure if it will help you, but its worth a shot. @drdam02

@jovandeginste
Copy link

@velocity303 @drdam02 if you're running puppet server, you may want to enable the ruby-2 compatibility (which gives you the option to upgrade the vault gem to latest)

  • With puppet 4:
    In puppetserver.conf, add this in the section jruby-puppet:
    compat-version: 2.0
  • With puppet 5:
    In /etc/sysconfig/puppetserver, add this line:
    JRUBY_JAR=/opt/puppetlabs/server/apps/puppetserver/jruby-9k.jar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants