Issue #11317 has been updated by Jacob McCann.
As Peter said, these don't just show up with summarize but in actual reports as
well:
<pre>
host:/var/lib/puppet/state # grep skip last_run_summary.yaml
skipped: 6
host:/var/lib/puppet/state # grep Sched last_run_report.yaml
"Schedule[daily]": !ruby/object:Puppet::Resource::Status {}
"Schedule[monthly]": !ruby/object:Puppet::Resource::Status {}
"Schedule[hourly]": !ruby/object:Puppet::Resource::Status {}
"Schedule[never]": !ruby/object:Puppet::Resource::Status {}
"Schedule[weekly]": !ruby/object:Puppet::Resource::Status {}
"Schedule[puppet]": !ruby/object:Puppet::Resource::Status {}
</pre>
Which shows up in foreman for me as well.
----------------------------------------
Bug #11317: Supposedly hidden skipped resources show up with --summarize
https://projects.puppetlabs.com/issues/11317#change-58184
Author: Christian Birch
Status: Investigating
Priority: Normal
Assignee:
Category: RAL
Target version:
Affected Puppet version: 2.7.8
Keywords: skipped resources debug summarize
Branch:
With 2.7.6 (also tested with 2.7.8), skipped resources - that are only visible
in debug mode - will show up as "skipped" with --summarize, even though debug
mode is not enabled. Prior to upgrading to 2.7.x, those skipped resources would
be hidden from --summarize.
Applying any manifest shows the issue. I'm using an empty manifest (test.pp)
below:
<pre>
# puppet apply --summarize -v -d test.pp
debug: Creating default schedules
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does
not exist
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist
debug: Failed to load library 'ldap' for feature 'ldap'
debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring
File[/var/lib/puppet/ssl/certs]
debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/private]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring
File[/var/lib/puppet/ssl]
debug: Finishing transaction -611357508
debug: Loaded state in 0.13 seconds
debug: Loaded state in 0.04 seconds
info: Applying configuration version '1323468413'
debug: /Schedule[daily]: Skipping device resources because running on a host
debug: /Schedule[monthly]: Skipping device resources because running on a host
debug: /Schedule[hourly]: Skipping device resources because running on a host
debug: /Schedule[never]: Skipping device resources because running on a host
debug: /Schedule[weekly]: Skipping device resources because running on a host
debug: /Schedule[puppet]: Skipping device resources because running on a host
debug: Finishing transaction -611605558
debug: Storing state
debug: Stored state in 0.59 seconds
notice: Finished catalog run in 0.73 seconds
Changes:
Events:
Resources:
Skipped: 6
Total: 7
Time:
Filebucket: 0.00
Config retrieval: 0.16
Total: 0.16
Last run: 1323468415
debug: Finishing transaction -610226698
debug: Received report to process from
ip-10-250-113-51.eu-west-1.compute.internal
debug: Processing report from ip-10-250-113-51.eu-west-1.compute.internal with
processor Puppet::Reports::Store
</pre>
OK, so 6 skipped resources (the Schedule-resources) which might be expected to
show up in debug mode. Anyway, not enabling debug mode does the same thing:
<pre>
# puppet apply --summarize -v test.pp
info: Applying configuration version '1323468385'
notice: Finished catalog run in 0.72 seconds
Changes:
Events:
Resources:
Skipped: 6
Total: 7
Time:
Filebucket: 0.00
Config retrieval: 0.13
Total: 0.13
Last run: 1323468387
</pre>
6 skipped resources which should probably be hidden when debug mode is not
enabled.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
