So the problem ended up being the python module - it was not the latest
version and it was adding custom resources which ignored what is in the
global config.
The 3 files which were causing the problems were;
python_version.rb
pip_version.rb
virtualenv_version.rb
The newer version have a
You could start checking your manifest dir for your environment :
puppet master --configprint manifest
mine says :
/data/puppet/environments/production/manifests
There you should have your site.pp for that environment.
hth
Johan
On 09/02/15 05:56, David LeVene wrote:
Hey All,
I've
Hi John,
To clarify, this should only be run on the puppet master as that's where
the catalog complication takes place?
That seems to be all good - the base environment points to production and
other environments point to their correct location.
puppet_master ~]# puppet master --configprint
Hey All,
I've started to upgrade a few puppet clients to the latest version and have
hit the issue which everyone had a while ago around this error
Warning: The package type's allow_virtual parameter will be changing its
default value from false to true in a future release. If you do not want
