Description of problem:
It was reported that some installations of the insights client do not report on a daily basis when used on client machines like laptops. This may be caused by the way how the insights-client.timer configuration is defined.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install and enable insights-client
2. Start the machine after 0:0:0
3. See insights-client not firing up
Insights client does not get triggered
Insights client gets started on a daily basis
According to the .timer configuration the client should be fired up "daily" - by systemd.time this has the following definition: "daily → *-*-* 00:00:00" - which is exactly at 0:0:0.
With the addition of "Persistant=True" a trigger of the client should be followed up even when the system had not been started at this time.
From "man systemd.timer":
Takes a boolean argument. If true, the time when the service unit was last triggered is stored on disk. When the timer is activated, the service unit is triggered immediately if it would have been triggered at least once during the time when the timer was inactive. This is useful to catch up on
missed runs of the service when the machine was off. Note that this setting only has an effect on timers configured with OnCalendar=.
Pavol, is this released and good now? Move to closed currentrelease if so.
Fix is ready and it will be available in next RHEL7/8 insights-client RPM release.
Pavol, has this been released yet? If not, can you please give an idea as to when? TY