Re: [Puppet Users] Skipped schedule resources in reports

2011-11-29 Thread flex
i met this problem too, and also don't know why some resource's type turned
into Schedule, are there someone can give me a reason?

On Tue, Sep 6, 2011 at 10:21 PM, Greg Sutcliffe greg.sutcli...@gmail.comwrote:

 Hi all,

 Since upgrading a few test machines from 2.6.7 to 2.7.3, I've noticed
 something slightly odd. Every single run reports 6 skipped resources, yet
 the reports are empty - they only state the execution time as per
 usual). On digging further it seems that the auto-generated Schedule
 resources (type/schedule.rb, line 307) are the entities being skipped,
 presumably because I'm not using them in any of my manifests.

 This is leading to a lot of reports with spurious data in them - since I
 don't use schedules, why should I care that Puppet skipped the default
 ones? This wouldn't be an issue, but I'm processing the reports and
 producing emails which summarize activity in the last hour, so for every
 2.7.3 node, I'm seeing 12 skipped resources per hour, which is noise that
 swamps the real data of resources that have changed for good reason.

 Is there a way to disable these default schedules, or the reporting of
 them? I tried --ignoreschedules on the commandline, but I get the
 impression that this causes other resources to run outside their normal
 schedule, rather than disabling the schedules themselves.

 As a hack, I added return Array.new to the self.mkdefaultschedules
 listed above, which stops the resources being generated, but this seems an
 ugly hack, and one I seem to have to make on every node. Is there a better
 way?

 Regards,
 Greg

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To view this discussion on the web visit
 https://groups.google.com/d/msg/puppet-users/-/KUcUT4hu148J.
 To post to this group, send email to puppet-users@googlegroups.com.
 To unsubscribe from this group, send email to
 puppet-users+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/puppet-users?hl=en.




-- 
System Administrator, Focus on System Management and Basic Development

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.



Re: [Puppet Users] Skipped schedule resources in reports

2011-11-29 Thread flex
oh, i make a mistake, the schedule resources are not turned from other
resources, they are created by default.
my puppet is 2.7.6

On Tue, Nov 29, 2011 at 5:49 PM, flex frostyn...@gmail.com wrote:

 i met this problem too, and also don't know why some resource's type
 turned into Schedule, are there someone can give me a reason?


 On Tue, Sep 6, 2011 at 10:21 PM, Greg Sutcliffe 
 greg.sutcli...@gmail.comwrote:

 Hi all,

 Since upgrading a few test machines from 2.6.7 to 2.7.3, I've noticed
 something slightly odd. Every single run reports 6 skipped resources, yet
 the reports are empty - they only state the execution time as per
 usual). On digging further it seems that the auto-generated Schedule
 resources (type/schedule.rb, line 307) are the entities being skipped,
 presumably because I'm not using them in any of my manifests.

 This is leading to a lot of reports with spurious data in them - since I
 don't use schedules, why should I care that Puppet skipped the default
 ones? This wouldn't be an issue, but I'm processing the reports and
 producing emails which summarize activity in the last hour, so for every
 2.7.3 node, I'm seeing 12 skipped resources per hour, which is noise that
 swamps the real data of resources that have changed for good reason.

 Is there a way to disable these default schedules, or the reporting of
 them? I tried --ignoreschedules on the commandline, but I get the
 impression that this causes other resources to run outside their normal
 schedule, rather than disabling the schedules themselves.

 As a hack, I added return Array.new to the self.mkdefaultschedules
 listed above, which stops the resources being generated, but this seems an
 ugly hack, and one I seem to have to make on every node. Is there a better
 way?

 Regards,
 Greg

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To view this discussion on the web visit
 https://groups.google.com/d/msg/puppet-users/-/KUcUT4hu148J.
 To post to this group, send email to puppet-users@googlegroups.com.
 To unsubscribe from this group, send email to
 puppet-users+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/puppet-users?hl=en.




 --
 System Administrator, Focus on System Management and Basic Development




-- 
System Administrator, Focus on System Management and Basic Development

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.