Issue #5086 has been updated by Jacob Helwig.
Andrew, What do you get if you do `facter | grep uptime`? Looking at the code in 1.5.8 for how the `uptime` fact is generated, it doesn't take years into account at all, so I'm not sure why you'd be getting this strange result. It looks like `uptime_seconds` would have to come back incorrectly. Thanks, Jacob ---------------------------------------- Bug #5086: Uptime reporting incorrectly for server where uptime is over on year https://projects.puppetlabs.com/issues/5086 Author: Andrew Heichelbech Status: Unreviewed Priority: Normal Assignee: Category: Target version: Keywords: Branch: The uptime is facter is reporting incorrecly. [/opt/csw/bin] # uptime 7:04pm up 588 day(s), 19:12, 4 users, load average: 0.05, 0.05, 0.05 [/opt/csw/bin] # facter uptime 223 days It does not seem the facter module for uptime takes into account years. If we subtract the 223 from the actual 588 it leaves 365, so somewhere in the processing I the time for 1 year has been lost. Environment information: OS version: Solaris 10 Update 6 Kernel version: Generic_138889-03 Puppet version: 0.25.5 Facter version: 1.5.8 Hardware: Sun Microsystems Sun Fire X4200 M2 -- 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.
