Closed Bug 805509 (b-2008-ix-0041) Opened 12 years ago Closed 9 years ago

b-2008-ix-0041 problem tracking

Categories

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

x86_64
Windows Server 2008

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

Details

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

Last job was 8 days, 0:50:18 ago.
rebooted.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Following a nagios report of PING failure a System Recovery dialog was found on the console. After failing to type the current Administrator password a few times (not the current or recent previous values for root) it rebooted and came up normally. Nothing obvious in the job history, just an example of bug 802539 three builds ago then two green birch-win32 builds. Kittenherder probably rebooted it after some idle time. Worth keeping an eye on.
Product: mozilla.org → Release Engineering
jhopkins, assigning while you look a little deeper into what was the root cause of bug 906660.
There might not be the need to look deeper into it if bhearsum is going to be fixing the IP banning, however, I thought of keeping good track of the investigation (if any is left).
Assignee: nobody → jhopkins
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Regarding the incorrect IPMI username/password, I changed the username to 'releng' in https://github.com/mozilla/briar-patch/commit/47b7cb52b6ea1b8580e283a43dcf7192982fe702 and updated the secrets file.  Verified by using kittenherder to IPMI-reboot a w64 build slave.
Assignee: jhopkins → armenzg
been running jobs fine for awhile
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → FIXED
Assignee: armenzg → nobody
QA Contact: armenzg → bugspam.Callek
Alias: w64-ix-slave64 → b-2008-ix-0041
Summary: w64-ix-slave64 problem tracking → b-2008-ix-0041 problem tracking
Status: RESOLVED → REOPENED
Depends on: 1198317
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 11 years ago9 years ago
Resolution: --- → FIXED
allocated to bug 1198317
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
deallocated from bug 1198317
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
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.