Actions
Bug #20350
closedgitgc is always run at start whatever its schedule is and run every 3~4 min
Status:
Released
Priority:
N/A
Assignee:
Category:
System integration
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
We have a cron to configure gitgc. By default, it should run every night (3h42).
But when we start rudder, whatever the time, we see that gitgc runs.
Plus, the log write a class instance name in place of the schedule.
Plus it runs every 3min42 because the cron format has seconds.
Updated by François ARMAND about 3 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 3 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder/pull/4035
Updated by François ARMAND about 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|55b0128c2d6e8cb305ae6f1e1b65d1c0b74bc12e.
Updated by François ARMAND about 3 years ago
- Subject changed from gitgc is always run at start whatever its schedule is and run every 3min42 to gitgc is always run at start whatever its schedule is and run every 3~4 min
I have no idea about the restart every 3~4min. Nothing seems to implies that. Perhaps the repeat
had a strange side effect, but I wasn't able to reproduce it.
The PR corrects the other problems.
Updated by Vincent MEMBRÉ about 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.0.0~rc2 which was released today.
Actions