[Puppet - Bug #8195] (Duplicate) postrun_command should run after reports and summaries
2011-07-01 17:15:52 GMT
- Status changed from Unreviewed to Duplicate
Dupe of #7127, I checked the code for 2.7.1 and didnt see it fixed there but its fixed in 2.6.9 already and 2.7.2 apparently.
- Author: R.I. Pienaar
- Status: Duplicate
- Priority: Normal
- Target version:
- Affected Puppet version: 2.6.8
At present the postrun_command is being run before the reports are sent and therefore also before they are stored locally in lastrunfile and lastrunreport.
This also has the very undesirable effect that a failure in the post run command will prevent reports from being sent:% puppet --report test.pp % ls -l /home/rip/.puppet/var/state/last* -rw-rw---- 1 rip rip 7374 Jul 1 18:05 /home/rip/.puppet/var/state/last_run_report.yaml -rw-rw---- 1 rip rip 283 Jul 1 18:05 /home/rip/.puppet/var/state/last_run_summary.yaml
Now we cause the post script to fail, reports not being written:% date Fri Jul 1 18:07:03 BST 2011 % puppet --report --postrun_command=/bin/false test.pp Could not run command from postrun_command: Execution of '/bin/false' returned 1: % ls -l /home/rip/.puppet/var/state/last* -rw-rw---- 1 rip rip 7374 Jul 1 18:05 /home/rip/.puppet/var/state/last_run_report.yaml -rw-rw---- 1 rip rip 283 Jul 1 18:05 /home/rip/.puppet/var/state/last_run_summary.yaml
It seems that a common case would be to process these files after runs and this command preventing reports being sent/written is a bad thing. Would be good if the code can Puppet::Configurer#run could be tweaked.
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.