Autocert cron time should be set to now() + random time
Bug #1862752 reported by
Benjamin Allot
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
autocert-charm |
Fix Released
|
Medium
|
Haw Loeung |
Bug Description
In the event of the juju controller flaps and the changed-hook is fired, the cron job time is rewritten.
However it doesn't account for the current time and could be set in the past.
That's fine until the controller flaps several time and prevent subsequent run to occur for several days.
I suggest to keep a range making restricted to few hours (say 00-06 AM UTC) or now() + 4 hours, or any idea that come up to mitigate the issue.
Regards,
Related branches
~hloeung/autocert-charm:master
- Benjamin Allot: Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 26 lines (+5/-3)1 file modifiedreactive/autocert.py (+5/-3)
Changed in autocert-charm: | |
assignee: | nobody → Haw Loeung (hloeung) |
importance: | Undecided → Medium |
status: | New → Fix Committed |
Changed in autocert-charm: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.