Puppet 3.6.0 'issues'

[Stefan Heijmans]

Hello,

Just upgraded Puppet from 3.4.3 to 3.6.0 in our sandbox, noticed the following.

-  directory environments
Documentation says; "Set environmentpath = $confdir/environments in the puppet master’s puppet.conf (in the [master] or [main] section)."
Except environmentpath does not work in the [master] section, [main] section works fine
Checked with; puppet config print and value is empty when specified in [master] section.

- puppet run now shows warnings on file resources with sourceselect for files which are not available in <module>/files directory.

May 16 10:58:41 <hostname> puppet-agent[21561]: Find /tst/file_metadata/modules/iptables/iptables-config_iptables-1.4.7-11.el6.x86_64.<hostname>?links=manage&source_permissions=use resulted in 404 with the message: Not Found: Could not find file_metadata modules/iptables/iptables-config_iptables-1.4.7-11.el6.x86_64.<hostname>

  file { '/etc/sysconfig/iptables-config' :
    ensure       => present,
    owner        => 'root',
    group        => 'root',
    mode         => $iptables::params::mode_sysconfig,
    source       =>
      [
      "puppet:///modules/iptables/iptables-config_${::iptablesversion}.${::hostname}",
      "puppet:///modules/iptables/iptables-config_${::iptablesversion}"
      ],
    sourceselect => first,
  }

ll iptables/files/iptables-config_iptables-1.4.7-11*
-rw-r-----. 1 puppet puppet 1974 Feb 26  2013 files/iptables-config_iptables-1.4.7-11.el6.x86_64

- puppet run on the puppet master, facts loaded twice, from modules directory and /var/lib/puppet

Info: Retrieving plugin
Info: Loading facts in /etc/puppet/environments/tst/modules/netbackup/lib/facter/netbackup_agent_version.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/netbackup/lib/facter/netbackup.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/multipath/lib/facter/lvm2version.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/multipath/lib/facter/multipathversion.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/common/lib/facter/vendor.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/common/lib/facter/runlevel.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/common/lib/facter/ictro_status.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/common/lib/facter/swap.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/selinux/lib/facter/c_selinux.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/vmware/lib/facter/vmware_tools_version.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/vmware/lib/facter/vmware_esx_version.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/ad/lib/facter/winbind.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/stdlib/lib/facter/puppet_vardir.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/stdlib/lib/facter/root_home.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/stdlib/lib/facter/facter_dot_d.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/stdlib/lib/facter/pe_version.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/dell/lib/facter/omsa_version.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/ovo/lib/facter/ovo_agent_version.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/puppet/lib/facter/os_version.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/ssh/lib/facter/sshdversion.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/oracle/lib/facter/oracle.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/iptables/lib/facter/iptables.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/iptables/lib/facter/iptablesversion.rb
Info: Loading facts in /var/lib/puppet/lib/facter/multipathversion.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ovo_agent_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/vmware_esx_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/vmware_tools_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/lvm2version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/netbackup.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptables.rb
Info: Loading facts in /var/lib/puppet/lib/facter/sshdversion.rb
Info: Loading facts in /var/lib/puppet/lib/facter/omsa_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/vendor.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptablesversion.rb
Info: Loading facts in /var/lib/puppet/lib/facter/oracle.rb
Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
Info: Loading facts in /var/lib/puppet/lib/facter/os_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/netbackup_agent_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ictro_status.rb
Info: Loading facts in /var/lib/puppet/lib/facter/c_selinux.rb
Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/winbind.rb
Info: Loading facts in /var/lib/puppet/lib/facter/swap.rb
Info: Loading facts in /var/lib/puppet/lib/facter/runlevel.rb

Stefan

[Felix Frank]

On 05/16/2014 11:20 AM, Stefan Heijmans wrote:
> - directory environments
> Documentation says; "Set environmentpath = $confdir/environments in the
> puppet master’s puppet.conf (in the [master] or [main] section)."
> Except environmentpath does not work in the [master] section, [main]
> section works fine
> Checked with; puppet config print and value is empty when specified in
> [master] section.

Hmm,

about this one - that doesn't look correct to me.

To see config as loaded by a master process, try

puppet master --configprint all

The other issues look legitimate to me, although the dual loading of
ruby code reminds me of some configuration issue that we helped at least
one other user fix in the past...

Thanks,
Felix

[Stefan Heijmans]

Hi Felix,

 

>>puppet master --configprint all

Does show that environmentpath is set when placed in [master] section, except client cannot find is modules anymore.

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class vmware for <fqdn> on node <fqn>

 

>>some configuration issue

Aha, if you could dig this up, that would be nice.

 

Stefan

[Chuck]

I can confirm all three of these issues in my environment also.

The environmentpath works in [main] only.  Even though configprint shows it is still there when moved to [master] and the modulepath looks correct also, but the puppet master does not find any of the modules.

# puppet master --configprint environmentpath
/var/opt/puppet/environments

# puppet master --configprint modulepath
/var/opt/puppet/environments/production/modules:/var/opt/puppet/environments/production/custom_modules:/var/opt/puppet/environments/production/custom_profile_modules

# cat /var/opt/puppet/environments/production/environment.conf
modulepath = modules:custom_modules:custom_profile_modules

[Chuck]

I opened a ticket for the environmentpath issue.

https://tickets.puppetlabs.com/browse/PUP-2607

[Josh Partlow]

On Friday, May 16, 2014 2:20:35 AM UTC-7, Stefan Heijmans wrote:

Hello,

Just upgraded Puppet from 3.4.3 to 3.6.0 in our sandbox, noticed the following.

-  directory environments
Documentation says; "Set environmentpath = $confdir/environments in the puppet master’s puppet.conf (in the [master] or [main] section)."
Except environmentpath does not work in the [master] section, [main] section works fine
Checked with; puppet config print and value is empty when specified in [master] section.

- puppet run now shows warnings on file resources with sourceselect for files which are not available in <module>/files directory.

Hi Stefan,

To see the [master] settings from a `puppet config print` you need to inform the config face that it should use that section, otherwise it defaults to [main] as a user run mode face.

`puppet config print environmentpath modulepath --section master`

for example, should print the environmentpath and modulepath as set in the master section.  Or you can use the `puppet master --configprint environmentpath,modulepath` variation that Felix mentioned.

 

May 16 10:58:41 <hostname> puppet-agent[21561]: Find /tst/file_metadata/modules/iptables/iptables-config_iptables-1.4.7-11.el6.x86_64.<hostname>?links=manage&source_permissions=use resulted in 404 with the message: Not Found: Could not find file_metadata modules/iptables/iptables-config_iptables-1.4.7-11.el6.x86_64.<hostname>

  file { '/etc/sysconfig/iptables-config' :
    ensure       => present,
    owner        => 'root',
    group        => 'root',
    mode         => $iptables::params::mode_sysconfig,
    source       =>
      [
      "puppet:///modules/iptables/iptables-config_${::iptablesversion}.${::hostname}",
      "puppet:///modules/iptables/iptables-config_${::iptablesversion}"
      ],
    sourceselect => first,
  }

ll iptables/files/iptables-config_iptables-1.4.7-11*
-rw-r-----. 1 puppet puppet 1974 Feb 26  2013 files/iptables-config_iptables-1.4.7-11.el6.x86_64

I think this issue is https://tickets.puppetlabs.com/browse/PUP-2584

 

- puppet run on the puppet master, facts loaded twice, from modules directory and /var/lib/puppet

Info: Retrieving plugin
Info: Loading facts in /etc/puppet/environments/tst/modules/netbackup/lib/facter/netbackup_agent_version.rb
Info: Loading facts in /etc/puppet/environments/tst/modules/netbackup/lib/facter/netbackup.rb

...

I may have lost the thread of what's happening here, but isn't the facts loaded from both modulepath and var lib dir just a consequence of having pluginsync'd on the master?

thanks,

Josh Partlow

Developer, Puppetlabs

Stefan

[Stefan Heijmans]

Hi Josh,

 

Thanks for your email.

 

>>but isn't the facts loaded from both modulepath and var lib dir just a consequence of having pluginsync'd on the master?

I mentioned it, as this behaviour didn't happen with 3.4.3.

 

I'll wait for the 3.6.1 release before testing any further.

 

Stefan

 

[Stefan Heijmans]

In 3.6.1 facts are also loaded twice when environmentpath is set in main-section of puppet.conf , see https://tickets.puppetlabs.com/browse/PUP-2651