Closed
Bug 1622943
Opened 5 years ago
Closed 5 years ago
lifecycle reregistrationTimeout of exactly 31 days causes errors
Categories
(Taskcluster :: Services, defect)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
Details
I suspect this is just a clock-skew thing? 30 days seems safe.
Assignee | ||
Comment 1•5 years ago
|
||
https://github.com/mozilla/community-tc-config/pull/242
If that works, I'll change the max value in the schema.
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → dustin
Assignee | ||
Updated•5 years ago
|
Summary: lifetime reregistrationTimeout of exactly 31 days causes errors → lifecycle reregistrationTimeout of exactly 31 days causes errors
Assignee | ||
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•