Issue #3959 has been updated by Nigel Kersten. Status changed from Needs Decision to Closed
I'm pretty sure we've resolved this one with configuration_version now being available at the top level of the report? <pre> --- !ruby/object:Puppet::Transaction::Report configuration_version: 1314835294 host: pe-debian5.localdomain kind: apply </pre> Closing and watching. ---------------------------------------- Feature #3959: reports should always include the config_version https://projects.puppetlabs.com/issues/3959 Author: R.I. Pienaar Status: Closed Priority: Normal Assignee: Nigel Kersten Category: Target version: Affected Puppet version: 0.25.5 Keywords: Branch: Currently only log events get tagged with the config version, which means unless something changes or emit logs you don't get any indication of config version that produced a report. this makes it hard to answer questions like when was the last config version that completed ok, since ok completions dont contain the version number only ones that fail or make changes. please add config_version to all reports. -- 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.
