Issue #7520 has been updated by Daniel Pittman. Status changed from Needs Decision to Accepted Assignee changed from Daniel Pittman to Max Martin Priority changed from High to Normal Target version changed from 3.X to Waldorf
Max has got it dead right in the summary. I have updated the schedule to reflect that. ---------------------------------------- Bug #7520: timestamp on reports should be taken from server, not client https://projects.puppetlabs.com/issues/7520#change-62498 Author: Chris Phillips Status: Accepted Priority: Normal Assignee: Max Martin Category: Target version: Waldorf Affected Puppet version: 2.6.7 Keywords: Branch: The timestamp on a report is taken from the report data sent by the client. If, for example, a new machine is being built and the system clock has not been set and ntp is not yet running and synchronized then the report can easily have a date in the future, or significantly in the past. The time of a report should come from the time that the puppetmaster believes it receives it and should not be taken directly from the data sent back by the client. I originally noticed this inconsistency in Dashboard, but is surely an issue coming out of Puppet (unless Dashboard has multiple timestamps to use and is making a bad choice of which one it uses) -- 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.
