Package Details: puppetserver 8.6.0-2

Git Clone URL: https://aur.archlinux.org/puppetserver.git (read-only, click to copy)
Package Base: puppetserver
Description: Server automation framework and application
Upstream URL: https://docs.puppetlabs.com/puppetserver/latest/services_master_puppetserver.html
Licenses: Apache
Submitter: aboe
Maintainer: lb.laboon (bastelfreak)
Last Packager: lb.laboon
Votes: 10
Popularity: 0.000000
First Submitted: 2014-09-26 19:48 (UTC)
Last Updated: 2024-08-19 13:53 (UTC)

Dependencies (7)

Required by (0)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

lb.laboon commented on 2023-09-20 20:33 (UTC) (edited on 2023-11-09 15:16 (UTC) by lb.laboon)

FYI to all users - I am aware that the package is currently out of date. I am purposefully holding back the package temporarily as there appears to be a major issue with the current latest version (8.2.1) preventing agents from getting catalogs.

Asking around upstream to see if I can get any assistance. It's possible this could be related to using a custom CA. Feel free to try the latest version for yourself and report back if it works for you or not.

Update: Puppet confirmed this issue. I will update the package once the fix has landed: https://github.com/puppetlabs/jvm-ssl-utils/pull/136

Update 2: The issue has been fixed in version 8.3.0. Package updated.

lb.laboon commented on 2020-05-11 14:34 (UTC)

@scarleo What is your locale set to? You might need to switch to a UTF-8 based locale.

scarleo commented on 2020-05-11 10:13 (UTC) (edited on 2020-05-11 12:24 (UTC) by scarleo)

What is up with that filename? EDIT: Ok, I get it, it's a check by filename, classy stuff :). Well turns out I didn't have UTF-8 locale in /etc/locale.conf, it's installing now, case closed.

Fetching hocon-1.2.5.gem
ERROR:  While executing gem ... (Java::JavaNioFile::InvalidPathException)
    Malformed input or input contains unmappable characters: /home/oscar/.cache/pikaur/build/puppetserver/pkg/puppetserver/opt/puppetlabs/server/data/puppetserver/vendored-jruby-gems/gems/hocon-1.2.5/spec/fixtures/test_utils/resources/ᚠᛇᚻ.conf
==> ERROR: A failure occurred in package().
    Aborting...

Command 'makepkg --force' failed to execute.

lb.laboon commented on 2020-04-25 21:52 (UTC)

@julius.tzm Actually facter is not bundled with this package at all. The gemspec file that this package now installs is basically just a "shim" to trick ruby into thinking that the facter dependency is satisfied. I agree that it seems really janky, but this actually how Puppetserver gets packaged for the official releases (I copied the gemspec file directly from the official RHEL 8 rpm).

julius.tzm commented on 2020-04-25 20:30 (UTC)

@lb.laboon, yes it works, however I would keep the facter version in sync with the main repo, but that is just a fancy thing.

Many thanks!

lb.laboon commented on 2020-04-25 18:51 (UTC)

@julius.tzm This should be fixed in the latest version. Please try upgrading

julius.tzm commented on 2020-04-25 12:09 (UTC)

Hi @ll,

puppetserver ca setup (04-25 13:59)

Traceback (most recent call last): 2: from /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca:3:in <main>' 1: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:inrequire' /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in require': cannot load such file -- puppetserver/ca/cli (LoadError) 8: from /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca:3:in<main>' 7: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:156:in require' 6: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:161:inrescue in require' 5: from /usr/lib/ruby/2.7.0/rubygems.rb:209:in try_activate' 4: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:inactivate' 3: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in activate_dependencies' 2: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:ineach' 1: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in block in activate_dependencies' /usr/lib/ruby/2.7.0/rubygems/dependency.rb:311:into_specs': Could not find 'facter' (>= 2.0.1, < 4) among 58 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/root/.gem/ruby/2.7.0:/usr/lib/ruby/gems/2.7.0', execute gem env for more information 9: from /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca:3:in <main>' 8: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:156:inrequire' 7: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:161:in rescue in require' 6: from /usr/lib/ruby/2.7.0/rubygems.rb:208:intry_activate' 5: from /usr/lib/ruby/2.7.0/rubygems.rb:215:in rescue in try_activate' 4: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:inactivate' 3: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in activate_dependencies' 2: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:ineach' 1: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in block in activate_dependencies' /usr/lib/ruby/2.7.0/rubygems/dependency.rb:311:into_specs': Could not find 'facter' (>= 2.0.1, < 4) among 58 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/root/.gem/ruby/2.7.0:/usr/lib/ruby/gems/2.7.0', execute gem env for more information

Does anybody has a clue how to solve this? After a fresh arch install, the facter 3.14.6-2 package is installed by default.

Thanks in advance!

devzero commented on 2019-03-22 19:40 (UTC)

@lb.laboon, thanks a lot, that did the trick. I'm still getting errors in the puppet client logs, but I think it's more of a misconfiguration issue rather than a problem with the package

lb.laboon commented on 2019-03-22 14:33 (UTC)

Hey @devzero, thanks for pointing that out! I use an external CA with my setup, so I hadn't noticed that was broken. I just updated the package so could you try updating? Let me know if that fixes the issue for you.

devzero commented on 2019-03-22 08:01 (UTC) (edited on 2019-03-22 08:10 (UTC) by devzero)

@lb.laboon Ah yes, I see, sorry about that. I was keyed on looking for /etc/puppetlabs/puppet, not "$confdir", so my brain deemed the pinned comment to be irrelevant :)

I did encounter another (unrelated) problem. Hopefully you can point me in the right direction again.

The puppetserver service starts without any problems, status looks good. Then I start puppet agent services on a couple of other boxes, using the standard Arch Linux puppet package. I now want to sign their certs.

On puppet master, I run sudo puppetserver ca list and get such errors:

/usr/sbin/puppetserver: /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca: /opt/puppetlabs/puppet/bin/ruby: bad interpreter: No such file or directory
/usr/sbin/puppetserver: line 80: /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca: Success

That path to /opt/puppetlabs/puppet/bin/ruby is hard-coded by /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca, but no ruby is installed in the stated location.

I tried patching that script to use the system installation of ruby, but this only produced more errors:

Traceback (most recent call last):
        2: from /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca:3:in `<main>'
        1: from /usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- puppetserver/ca/cli (LoadError)