Project

General

Profile

Bug #12

Last report entry missing and date incorrect

Added by Moty Lavi over 10 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Puppet Reports
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

After setting new foreman report feature I have two problems:

1) Clients that don't have the entry "report=true" in their puppet.conf stoped showing "last report" time in the hosts screen. This worked prior to last foreman reports feature

2) The clients that do have this entry set, report wrong "last report" time in the hosts screen ( "about 2 hours" for a client that got updated in the last minute" )

Associated revisions

Revision 0b8c48c4 (diff)
Added by Dominic Cleal almost 6 years ago

Remove external assets, use inline JavaScript

Debian packages can't compile assets yet.

Fixes #12

History

#1 Updated by Ohad Levy over 10 years ago

motyla wrote:

After setting new foreman report feature I have two problems:

1) Clients that don't have the entry "report=true" in their puppet.conf stoped showing "last report" time in the hosts screen. This worked prior to last foreman reports feature

True, in the database we store both last_compile and last_report, the difference is that last_report means that puppet ran and did everything (or not) it was suppose to do, last_compile just means the server sent a compilation to the client, but it might not actually work (e.g. duplicate definitions etc)

What I would like to do is to provide status indicators (maybe small status icons?)

2) The clients that do have this entry set, report wrong "last report" time in the hosts screen ( "about 2 hours" for a client that got updated in the last minute" )

Yeah, that's because I store in UTC and didnt convert it back...

#2 Updated by Moty Lavi over 10 years ago

status icon will differ between a client that was lately updated an one that did not ?

#3 Updated by Ohad Levy over 10 years ago

motyla wrote:

status icon will differ between a client that was lately updated an one that did not ?

yeah, for example:

host is kickstarting
host is installing
host had puppet failures
host did not run puppet in the last X time
host is disable
...

#4 Updated by Moty Lavi over 10 years ago

perfect

#5 Updated by Ohad Levy over 10 years ago

2) The clients that do have this entry set, report wrong "last report" time in the hosts screen ( "about 2 hours" for a client that got updated in the last minute" )

Yeah, that's because I store in UTC and didnt convert it back...

It seems that when store configs are enable, puppet will always store in local time vs. utc, since our app suppose to support many sites (usually in different time zones), we want to store our time in UTC.
and it seems that I've already encountered this problem and forgot about it - http://projects.reductivelabs.com/issues/2518

I'll see if I can fix it in puppet upstream.

however its a bit more complicated than that:
last_compile value, is actually set by puppet (when store configs are enable), if we are using the last_report we can get the right value if the db is set to use utc (will I'll report in another bug).

I think that I'll enable utc on our db, then the last compile value will not be correct, but last report will.

#6 Updated by Ohad Levy over 10 years ago

  • Status changed from New to Ready For Testing
  • % Done changed from 0 to 100

#7 Updated by Ohad Levy over 10 years ago

  • Status changed from Ready For Testing to Closed

#8 Updated by Ohad Levy over 10 years ago

  • Target version set to 0.1-1

Also available in: Atom PDF