Closed
Bug 848488
Opened 12 years ago
Closed 12 years ago
release runner shouldn't send e-mail about slow reconfig until it's more sure there's a problem
Categories
(Release Engineering :: Release Automation, defect)
Release Engineering
Release Automation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
Details
(Whiteboard: [shipit])
Attachments
(1 file)
|
1.46 KB,
patch
|
rail
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
Currently, release runner sends warnings about reconfigs not completing every 5min. However, the AWS masters can take upwards of 20min to reconfig (as I understand it). This is problematic because it makes it appear like someone needs to take action when they often don't. We should either:
1) Make release runner wait longer before sending mail
2) Make the AWS masters reconfig faster
Or maybe do both.
Flags: needinfo?(catlee)
Comment 1•12 years ago
|
||
I don't think 2) is going to be easy
5 minutes is a bit aggressive for 1). let's change it to 10 or 15, and adjust the message to say that you shouldn't be alarmed until 30 minutes have gone by?
Flags: needinfo?(catlee)
| Assignee | ||
Comment 3•12 years ago
|
||
Implements #1. I got rid of the timedelta because I think "600 seconds" is more readable than "0:05:00.117830"
Attachment #722801 -
Flags: review?(rail)
Updated•12 years ago
|
Attachment #722801 -
Flags: review?(rail) → review+
| Assignee | ||
Comment 4•12 years ago
|
||
Comment on attachment 722801 [details] [diff] [review]
adjust message; times
Landed, updated the checkout on bm36, and restarted release runner through supervisorctl.
Attachment #722801 -
Flags: checked-in+
| Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•