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 puppet/u
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
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 'puppet/type/pac
Could you post the content of package_provider.rb? Since that is in
cache/lib/facter, it is a custom fact and the specifics of its
implementation could shed some light on what is happening.
-Charlie
On Thursday, June 20, 2019 at 1:53:34 PM UTC-7, Patrick Whitney wrote:
>
> Hello Everyone,
>
>
