Closed Bug 828622 (tegra-327) Opened 11 years ago Closed 11 years ago

tegra-327 problem tracking

Categories

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

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Unassigned)

References

()

Details

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

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)
pdu reboot requested
Didn't work, off to recovery.
Depends on: 825335
reimaged, no card swap.
Looks like its been taking jobs
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
9 days, 16:16:00 since last job
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
back in production
Status: REOPENED → RESOLVED
Closed: 11 years ago11 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
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
we can't seem to keep this device up --> decomm
Status: RESOLVED → REOPENED
Depends on: tegra-decomm
Resolution: FIXED → ---
decommed
Status: REOPENED → RESOLVED
Closed: 11 years ago11 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.