If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.
Bug 828622 (tegra-327)

tegra-327 problem tracking

RESOLVED FIXED

Status

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

People

(Reporter: bhearsum, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

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

(Reporter)

Description

5 years ago
15:09 < nagios-releng> Wed 12:09:36 PST [411] tegra-327.build.mtv1.mozilla.com:tegra agent check is CRITICAL: Connection refused (http://m.allizom.org/tegra+agent+check)
(Reporter)

Comment 1

5 years ago
pdu reboot requested
(Reporter)

Comment 2

5 years ago
Didn't work, off to recovery.
Depends on: 825335

Comment 3

5 years ago
reimaged, no card swap.
Looks like its been taking jobs
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Reporter)

Comment 5

5 years ago
9 days, 16:16:00 since last job
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Reporter)

Comment 6

5 years ago
back in production
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → FIXED
And it did four jobs, three green and one retry, and then stopped again.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
manual pdu reboot brought it back to life
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago4 years ago
Resolution: --- → FIXED

Updated

4 years ago
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
we can't seem to keep this device up --> decomm
Status: RESOLVED → REOPENED
Depends on: 918168
Resolution: FIXED → ---
(Reporter)

Comment 10

4 years ago
decommed
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.