Bug 795791 (b-2008-ix-0087)

b-2008-ix-0087 problem tracking

RESOLVED FIXED

Status

Release Engineering
Buildduty
P3
normal
RESOLVED FIXED
5 years ago
3 years ago

People

(Reporter: philor, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

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

(Reporter)

Description

5 years ago
Last job was 40 days, 22:53:26 ago.
Autologon wasn't enabled on this machine. I fixed it and put into production. I'll be keeping an eye on it.
Green build
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
Status: RESOLVED → REOPENED
Depends on: 930671
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago4 years ago
Resolution: --- → FIXED
Alias: w64-ix-slave28 → b-2008-ix-0087
Summary: w64-ix-slave28 problem tracking → b-2008-ix-0087 problem tracking
Depends on: 1019165
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
No longer depends on: 1019165

Updated

3 years ago
Depends on: 1046522
Depends on: 1046574
Attempting SSH reboot...Failed.
Attempting IPMI reboot...Failed.
Filed IT bug for reboot (bug 1046574)
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.
(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.
rebooted to production
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.