Project

General

Profile

Feature #161

No way to indicate multiple puppet intervals

Added by Dis Connect over 12 years ago. Updated almost 10 years ago.

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

Description

We have multiple classes of client with several puppet run intervals. (For example, the memcache servers run every 6 hours due to the high IO load puppet imposes, which frequently results in memcached timeouts.) There is no way to associate a tag/class with a run interval in foreman, so these servers are perpetually listed as outdated.

History

#1 Updated by Ohad Levy over 12 years ago

  • Status changed from New to Feedback
  • Assignee changed from Ohad Levy to Dis Connect

I gave this some more thought, and I'm not 100% sure its a good idea.
one small bug in puppet, is that sometimes it sends the same report twice, in order not to import it again, I validate that there is only one report per host per a certain time, this will not work if I'll keep the server local time instead.

I do keep the creation time of the report in the db as well, would it be ok as a work around to expire reports based on their creation time in the db instead of their reported time? this will fix the issue with unable to expire reports that have a wrong date.

additionally, I can write errors to the log if the report time is different to the current time (e.g. +1 one hour in utc).

#2 Updated by Dis Connect over 12 years ago

  • Assignee changed from Dis Connect to Ohad Levy

Assigned to me somehow, assigning it back. (Also, that comment was for a different bug - this is about long-interval hosts.)

#3 Updated by Ohad Levy about 11 years ago

  • Assignee deleted (Ohad Levy)

#4 Updated by Ohad Levy about 10 years ago

  • Tracker changed from Bug to Feature

#5 Updated by Benjamin Papillon almost 10 years ago

  • Status changed from Feedback to New

Also available in: Atom PDF