Well, geez. When it rains, it pours. When runnin...
# voxpupuli
b
Well, geez. When it rains, it pours. When running "puppetserver ca <anything>" ruby is very cranky. If I run "puppetserver <any other command>" then everything is fine. When I run 'puppetserver ca list --all' I get the errors:
Copy code
/opt/puppetlabs/puppet/lib/ruby/3.2.0/rubygems/specification.rb:1466:in `rescue in block in activate_dependencies': Could not find 'facter' (>= 2.0.1, < 5) among 122 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/root/.gem/ruby/3.2.0:/opt/puppetlabs/puppet/lib/ruby/gems/3.2.0:/opt/puppetlabs/puppet/lib/ruby/vendor_gems' at: /opt/puppetlabs/puppet/lib/ruby/vendor_gems/specifications/puppetserver-ca-2.6.0.gemspec, execute `gem env` for more information
        from /opt/puppetlabs/puppet/lib/ruby/3.2.0/rubygems/specification.rb:1463:in `block in activate_dependencies'
        from /opt/puppetlabs/puppet/lib/ruby/3.2.0/rubygems/specification.rb:1452:in `each'
        from /opt/puppetlabs/puppet/lib/ruby/3.2.0/rubygems/specification.rb:1452:in `activate_dependencies'
        from /opt/puppetlabs/puppet/lib/ruby/3.2.0/rubygems/specification.rb:1434:in `activate'
        from /opt/puppetlabs/puppet/lib/ruby/3.2.0/rubygems.rb:210:in `rescue in try_activate'
        from /opt/puppetlabs/puppet/lib/ruby/3.2.0/rubygems.rb:203:in `try_activate'
        from <internal:/opt/puppetlabs/puppet/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:155:in `rescue in require'
        from <internal:/opt/puppetlabs/puppet/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:40:in `require'
        from /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca:3:in `<main>'
I've reinstalled openvox-agent and openvox-server but the errors persist. I've tried reinstalling the facter gem but still errors. I don't know how long this has been happening. The puppet server is behaving just fine outside of this. I have auto-sign turned on for my environment so new agents are checking it just fine. I'm trying to move some agents from my test environment back to the production environment so their old certs need pruning on the production environment. Any hints or ideas appreciated.