Bug #6718
closed
If the agent schedule is not every 5 minutes, inventory may not be sent anymore
Added by Nicolas CHARLES over 9 years ago.
Updated about 9 years ago.
Category:
System techniques
Description
If we don't have a 5 minutes schedume, inventory may never get updated anymore. Indeed, we only rely on splayclass(hourly), that is valid for 5 minutes every hours; so it is probably not ok for most schedule
hum, this is tricky, as it should work on 3.5
Idea: if schedule is standart, keep the splayclass, otherwise unconditionnaly execute the inventory ?
- Target version changed from 2.10.15 to 2.10.16
Does anyone has an idea on how to nicely fix that?
I'd advise either to:
- Compute the classes that define when to send the inventory ourselves in Rudder and generate them in the policies in accordance with the current agent execution
- Let something else that CFEngine handle the inventories (but I dislike this approach)
I don't have any other idea atm
- Target version changed from 2.10.16 to 2.10.17
- Related to Bug #6121: Some nodes may have outdated inventories on the server added
This is most likely causing #6121
Ok, an idea:
- use select_class to select between midnight and 6am
- compare run_interval:
if == 5, keep splayclass + select class
if between 5 and 60; keep only the select class
if more than 60, no condition
- Status changed from New to Pending technical review
- Assignee set to Matthieu CERDA
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/739/files
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.17, 2.11.14, 3.0.9 and 3.1.2 which were released today.
- Related to Bug #7290: Inventory upload is not distributed uniformly added
Also available in: Atom
PDF