-
Notifications
You must be signed in to change notification settings - Fork 229
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
Add shared gem path for Puppetserver >= 5.3 #630
Labels
Comments
This is kind of crucial because missing gems can introduce really ugly problems. See https://tickets.puppetlabs.com/browse/PUP-8715 |
baurmatt
added a commit
to syseleven/puppet-puppet
that referenced
this issue
Sep 19, 2018
Since 5.3.0 Puppet Server can use some gems shipped by puppet-agent. For this the gem-path settings of puppetserver.conf needs to be extend by /opt/puppetlabs/puppet/lib/ruby/vendor_gems. This is the default as shipped by Puppetlabs. Fixes theforemanGH-630.
baurmatt
added a commit
to syseleven/puppet-puppet
that referenced
this issue
Sep 28, 2018
Since 5.3.0 Puppet Server can use some gems shipped by puppet-agent. For this the gem-path settings of puppetserver.conf needs to be extend by /opt/puppetlabs/puppet/lib/ruby/vendor_gems. This is the default as shipped by Puppetlabs. Fixes theforemanGH-630.
ekohl
pushed a commit
that referenced
this issue
Oct 4, 2018
Since 5.3.0 Puppet Server can use some gems shipped by puppet-agent. For this the gem-path settings of puppetserver.conf needs to be extend by /opt/puppetlabs/puppet/lib/ruby/vendor_gems. This is the default as shipped by Puppetlabs. Fixes GH-630.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
puppet-puppet/templates/server/puppetserver/conf.d/puppetserver.conf.erb
Line 19 in 73f7fe6
This needs to be extend for Puppetserver >= 5.3 due to the introduced shared gem folder
/opt/puppetlabs/puppet/lib/ruby/vendor_gems
.I will provide a PR.
The text was updated successfully, but these errors were encountered: