Closed
Bug 795791
(b-2008-ix-0087)
Opened 12 years ago
Closed 10 years ago
b-2008-ix-0087 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Infrastructure & Operations Graveyard
CIDuty
x86_64
Windows Server 2008
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Unassigned)
References
Details
(Whiteboard: [buildduty][buildslaves][capacity])
Last job was 40 days, 22:53:26 ago.
Comment 1•12 years ago
|
||
Autologon wasn't enabled on this machine. I fixed it and put into production. I'll be keeping an eye on it.
Comment 2•12 years ago
|
||
Green build
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•11 years ago
|
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Alias: w64-ix-slave28 → b-2008-ix-0087
Updated•10 years ago
|
Summary: w64-ix-slave28 problem tracking → b-2008-ix-0087 problem tracking
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 3•10 years ago
|
||
Attempting SSH reboot...Failed. Attempting IPMI reboot...Failed. Filed IT bug for reboot (bug 1046574)
Comment 4•10 years ago
|
||
another false positive from slaveapi, there was a bug to ask them to be reimaged. slaveapi shouldn't be touching slaves that are in the process of installing lest it reboot them in the middle of the process.
Comment 5•10 years ago
|
||
(In reply to Amy Rich [:arich] [:arr] from comment #4) > another false positive from slaveapi, there was a bug to ask them to be > reimaged. slaveapi shouldn't be touching slaves that are in the process of > installing lest it reboot them in the middle of the process. I noticed this morning this slave had a reimage request, but was not disabled in slavealloc - probably the reason slaveapi raised bug 1046575. I disabled the slave in slave alloc. That said, I don't remember exactly what time I noticed and updated slave alloc - whether it was before or after comment 3.
Comment 6•10 years ago
|
||
rebooted to production
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•