Closed
Bug 810395
Opened 13 years ago
Closed 13 years ago
get release runner working under supervisord
Categories
(Release Engineering :: Release Automation, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: rail)
Details
(Whiteboard: [shipit])
* create a supervisord config with logging enabled
* create a simple wrapper which:
* starts release runner
* checks the return code
* in case of failure:
* send an email (and update the status in the DB?) about the failure with last N lines of code
* sleep 3 days (in case of weekend)
Also need to make sure that everything works w/out a tty available.
Assignee | ||
Updated•13 years ago
|
Whiteboard: [kickoff]
Assignee | ||
Updated•13 years ago
|
Priority: -- → P2
Assignee | ||
Comment 1•13 years ago
|
||
Just to update the WIP status. Everything listed above is done. We have some issues with logging though, see https://bugzilla.mozilla.org/show_bug.cgi?id=810393#c2. Maybe it's related to the fact that there no tty attached in this scenario.
Assignee | ||
Comment 2•13 years ago
|
||
It worked finally. We hit 2 issues:
1) the config file used ~/ssh/path_to_key. It turns out that HOME is not set under supervisor. changing the path to /home/cltbld/.ssh/path_to_key fixed the problem.
2) ~/.ssh/authorized_keys on bm25 and bm34 were out of sync (puppet issues). Restarting puppet on bm25 and adding the key to bm34 fixed the problem.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•13 years ago
|
Whiteboard: [kickoff] → [shipit]
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
•