Skip to content
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.

puppetserver_gem provider requires PATH to include path to puppetserver binary #47

Closed
davealden opened this issue Mar 3, 2017 · 2 comments

Comments

@davealden
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: any?
  • Ruby: any?
  • Distribution: any?
  • Module version: 2.2.0

How to reproduce (e.g Puppet code you use)

ensure('vault', {provider=>'puppetserver_gem'})

What are you seeing

Error: /Stage[main]/Profile::Puppetmaster/Package[vault]: Provider puppetserver_gem is not functional on this host

What behaviour did you expect instead

vault to be installed

Output log

Any additional information you'd like to impart

Looking at lib/puppet/provider/package/puppetserver_gem.rb I see that it does a which('puppetserver'), hence the requirement that it be in the path. But this is the only thing I've ever run in to that required puppetserver to be in the path when I run "puppet agent -t". The puppetlabs/puppetserver_gem module doesn't do a which, it hard codes it to the path -- maybe this should do the same?

@maxadamo
Copy link
Sponsor

maxadamo commented Feb 17, 2018

but, how about removing the puppetserver_gem support?
There is an official puppetserver_gem module: puppetserver_gem
but it's not possible to use that one along with this one: it keeps overwriting the ruby script at each run.

@ZeroPointEnergy
Copy link

Looks like this provider is no longer in the module in the most recent version. This can probably be closed?

@ekohl ekohl closed this as completed May 3, 2019
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

4 participants