Luke- After the last upgrade to puppet there was change in the yaml format for the facts yaml files. It looks like a time stamp has gotten accidently inserted in the file or miss formated: --- !ruby/object:Puppet::Node::Facts name: elephant.unix.eng.ua.edu values: :_timestamp: 2008-11-12 14:47:51.749544 -06:00 <<< this is the line in question. processorcount: "4" kernel: Linux processor2: Intel(R) XEON(TM) CPU 2.20GHz serialnumber: 5NHJL11 uniqueid: a0821114 lsbrelease: ":core-3.1-ia32:core-3.1-noarch:g I noticed it because it broke the puppetview fact reporting. If delete this line puppetview is able to correctly report facts again. If it si a bug I''ll make a bug report. If it is correct, then I will try and patch puppetview. Evan --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Nov 12, 2008, at 12:58 PM, Evan Hisey wrote:> > Luke- > After the last upgrade to puppet there was change in the yaml > format for the facts yaml files. It looks like a time stamp has gotten > accidently inserted in the file or miss formated: > > --- !ruby/object:Puppet::Node::Facts > name: elephant.unix.eng.ua.edu > values: > :_timestamp: 2008-11-12 14:47:51.749544 -06:00 <<< this is the > line in question. > processorcount: "4" > kernel: Linux > processor2: Intel(R) XEON(TM) CPU 2.20GHz > serialnumber: 5NHJL11 > uniqueid: a0821114 > lsbrelease: ":core-3.1-ia32:core-3.1-noarch:g > > > > > > I noticed it because it broke the puppetview fact reporting. If delete > this line puppetview is able to correctly report facts again. If it si > a bug I''ll make a bug report. If it is correct, then I will try and > patch puppetview.Well, the format didn''t get modified -- we just added an attribute. I''d just have it ignore that timestamp, although you can also use it to indicate the age of the information (although I think the Facts instance would have it as ''facts.timestamp''.) -- The cure for writer''s cramp is writer''s block. -- Inigo DeLeon --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
>> I noticed it because it broke the puppetview fact reporting. If delete >> this line puppetview is able to correctly report facts again. If it si >> a bug I''ll make a bug report. If it is correct, then I will try and >> patch puppetview. > > Well, the format didn''t get modified -- we just added an attribute. > > I''d just have it ignore that timestamp, although you can also use it > to indicate the age of the information (although I think the Facts > instance would have it as ''facts.timestamp''.) >Okay, I''ll code around the quirky format of that time stamp. I would have expexted it to look like: timestamp: 2008-11-12 14:47:51.749544 -06:00 instead of :_timestamp: 2008-11-12 14:47:51.749544 -06:00, that was why I want to check if it was a bug. Evan --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Nov 12, 2008, at 8:28 PM, Evan Hisey wrote:> >>> I noticed it because it broke the puppetview fact reporting. If >>> delete >>> this line puppetview is able to correctly report facts again. If >>> it si >>> a bug I''ll make a bug report. If it is correct, then I will try and >>> patch puppetview. >> >> Well, the format didn''t get modified -- we just added an attribute. >> >> I''d just have it ignore that timestamp, although you can also use it >> to indicate the age of the information (although I think the Facts >> instance would have it as ''facts.timestamp''.) >> > Okay, I''ll code around the quirky format of that time stamp. I would > have expexted it to look like: > timestamp: 2008-11-12 14:47:51.749544 -06:00 instead of :_timestamp: > 2008-11-12 14:47:51.749544 -06:00, that was why I want to check if it > was a bug.In looking at the code again... I think that can actually be removed. We now use an ''expiration'' attribute that comes from an Envelope module, so this looks obsolete. I''ll fix it. -- The world is round; it has no point. -- Adrienne E. Gusoff --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---