[Puppet Users] Re: Trouble after Agent upgrade -- Error: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)

2019-06-21 Thread Charlie Sharpsteen
A quick update on this one: With Patrick's help, we were able to re-produce the issue in AWS. The root cause appears to be that the Puppet::Provider class includes the Puppet::Util module, which also happens to have a Puppet::Util::Package sub-module. So, depending on the load order of

Re: [Puppet Users] Core Modules with Puppet pre6?

2019-06-21 Thread Josh Cooper
On Fri, Jun 21, 2019 at 12:51 AM Martin Alfke wrote: > > Hi, > > has anyone tried what will happen if we place the Puppet 6 core modules in a > Puppetfile when still having a Puppet 5.x agent? > Will the agent still use the built-in types/providers? > > e.g. > Puppetfile: > mod

Re: [Puppet Users] stdlib module causes puppet failure

2019-06-21 Thread Josh Cooper
On Thu, Jun 20, 2019 at 10:45 AM Michael Watters wrote: > > I'm having an issue with the puppetlabs-stdlib module causing compilation > failures using the puppet apply command. > > > Error: Class 'stdlib' is already defined (file: > >

[Puppet Users] Re: Trouble after Agent upgrade -- Error: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)

2019-06-21 Thread Jeff Cheng
We're seeing similar issues with the official v6.5.0 docker image when running in circleci: circleci@default-d4c9fa03-e104-4e3d-bb5e-3510a1a9eed8:~/project$ docker run --rm puppet/puppet-agent-ubuntu:6.5.0 resource --types Error: Could not autoload puppet/provider/package/gem: superclass must be

Re: [Puppet Users] fips and non fips agent rpms

2019-06-21 Thread Josh Cooper
On Thu, Jun 20, 2019 at 9:05 AM 'slig...@verizon.net' via Puppet Users wrote: > > Hello, > > We are using some fips and some non-fips agent. Proper agent rpm (fips or non > fips based on current configuration) has been installed, however, after agent > installation, if we were to update a agent

[Puppet Users] Re: Trouble after Agent upgrade -- Error: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)

2019-06-21 Thread Patrick Whitney
Hi Charlie, Thanks for the help! # Fact: package_provider # # Purpose: Returns the default provider Puppet will choose to manage packages # on this system # # Resolution: Instantiates a dummy package resource and return the provider # # Caveats: # require 'puppet/type' require

Re: [Puppet Users] Sensitive type?

2019-06-21 Thread Henrik Lindberg
On 2019-06-20 13:31, Jason McMahan wrote: Good day, We were attempting to secure passwords appearing in files. In the node manifest we changed $password = lookup("user_cred.${username}.${domain_lookup}.password")) to $password =

[Puppet Users] Core Modules with Puppet pre6?

2019-06-21 Thread Martin Alfke
Hi, has anyone tried what will happen if we place the Puppet 6 core modules in a Puppetfile when still having a Puppet 5.x agent? Will the agent still use the built-in types/providers? e.g. Puppetfile: mod 'puppetlabs/mount_core', :latest mod 'puppetlabs/augeas_core', :latest mod