The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
puppet generate yaml report file in a different GMT time that it was generated
|Affected Puppet version:||0.25.4||Branch:|
|Keywords:||report yaml gmt time|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
Puppet generate their yaml report files with GMT 0
However, if we look the time value within the yaml file body we ge the right machine time. In the example bellow, the machine’s GMT is -03:00 (I’ve added one more dash) .
—– !ruby/object:Puppet::Transaction::Report host: xxxx.globoi.com logs: – !ruby/object:Puppet::Util::Log level: :info message: Applying configuration version ‘1270595394’ source: Puppet tags: – info time: 2010-04-06 20:09:59.434711 —03:00 – !ruby/object:Puppet::Util::Log …
#5 Updated by Gustavo Soares almost 6 years ago
Jean-Yves LE ROUX wrote:
please could you avoid to delay anymore the resolution of this Bug because of impact on puppet dashboard.. see Bug #3512.. and for me the file name could contain the real time of the puppet server
I also think that the filename should contain the real time.