Closed Bug 731770 (linux64-ix-slave05) Opened 13 years ago Closed 13 years ago

linux64-ix-slave05 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86
macOS
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: armenzg, Unassigned)

References

Details

(Whiteboard: [buildduty][capacity][buildslaves])

Being re-imaged in bug 717996.
Priority: -- → P3
Whiteboard: [buildduty][capacity][buildslaves]
Summary: linux64-ix-slave05 → linux64-ix-slave05 problem tracking
Back in production.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Needs reimaging.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 762213
Back to production
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Loaning to ejpbruel in bug 772622.
Depends on: 772622
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: armenzg
Closing this because we don't track loans in these bugs AFAIK.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
No longer depends on: 772622
Resolution: --- → FIXED
Depends on: 772622
Depends on: 793814
This will need to be integrated back into production once it is re-imaged (bug 793814).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Kim, this has had its last job: 38 days, 9:27:57 but marked in slavealloc as yours, are you still using it? Or does Buildduty need to triage this?
Flags: needinfo?(kmoir)
I don't need it anymore, I've opened bug 813054 to reimage it.
Depends on: 813054
Flags: needinfo?(kmoir)
Looks like it made it back into production on 2012-12-10, and has since burned every job from not having the right keys, except when it disconnected in the middle of a couple of jobs before it got around to burning the upload step.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This slave somehow made it back into the production pool without getting the right keys on it. It just burned a release repack job because of it. I fixed the keys.
Oh, and I disabled it in slavealloc in case other things are wrong.
I went through the post re-image instructions and I believe this slave is in good shape again. I put it back in the production pool.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.