Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
-
RHEL 6.6 x86_64
Puppet 3.7.4
Facter 2.4.1
-
3
-
Server Jade 2016-04-20
Description
Hello,
I've just switched from apache/passenger to puppet server 1.0.2 in our sandbox (after switching from hiera-gpg to hiera-eyaml).
Doing some test runs shows the following in the pupppetserver.log file;
015-02-23 20:32:55,505 INFO [puppet-server] Puppet Not Found: Could not find file_metadata modules/mondo/3/tb/make_mondoarchive.sh..<hostname>
2015-02-23 20:42:50,916 INFO [puppet-server] Puppet Not Found: Could not find file_metadata modules/mondo/3/tb/make_mondoarchive.sh.<hostname>
2015-02-23 20:43:07,700 INFO [puppet-server] Puppet Not Found: Could not find file_metadata modules/mondo/3/tb/make_mondoarchive.sh..<hostname>
2015-02-23 20:43:13,963 INFO [puppet-server] Puppet Not Found: Could not find file_bucket_file md5/85b75b6e41c467513f4625947c84f1cc//etc/puppet/scripts/monthly_run.sh
2015-02-23 20:43:18,173 INFO [puppet-server] Puppet Not Found: Could not find file_metadata modules/mondo/3/tb/make_mondoarchive.sh.<hostname>
2015-02-23 20:43:36,080 INFO [puppet-server] Puppet Not Found: Could not find file_metadata modules/mondo/3/tb/make_mondoarchive.sh.<hostname>
2015-02-23 20:48:16,747 INFO [puppet-server] Puppet Not Found: Could not find file_metadata modules/mondo/3/tb/make_mondoarchive.sh.<hostname>
2015-02-23 20:51:34,403 INFO [puppet-server] Puppet Not Found: Could not find file_bucket_file md5/f4f7e01332717f3f591868a3dcd909ab//etc/sudoers
The file_metadata seems to happen on all resources with a sourceselect in the manifest.
make_mondoarchive.sh is done by a sourceselect (first) in the manifest like;
file { '/tb/jobs/system/make_mondoarchive.sh':
ensure => present,
owner => 'root',
group => 'root',
mode => '0700',
source => [ "puppet:///modules/mondo/${mondo::params::mondo_version}/tb/make_mondoarchive.sh.${::hostname}",
"puppet:///modules/mondo/${mondo::params::mondo_version}/tb/make_mondoarchive.sh.${mondo::params::mondo_nfs_version}",
"puppet:///modules/mondo/${mondo::params::mondo_version}/tb/make_mondoarchive.sh"],
sourceselect => first,
require => Class['mondo::install'],
}
That it cannot find those files is correct, as they don't exist on the filesystem.
With the apache/passenger setup we never had these messages, so we don't expect them with puppet server, correct?
Else there will be a load of these message when we use puppet server in out production environment.
Attachments
Issue Links
- relates to
-
SERVER-1257 Add section to docs to indicate puppet-server may be chattier in logs than passenger
-
- Closed
-
- links to