Status

RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: bear, Assigned: dividehex)

Tracking

Details

(Whiteboard: [buildduty][buildslave][tegra])

Comment hidden (empty)
(Reporter)

Updated

7 years ago
See Also: → bug 754391
(Reporter)

Updated

7 years ago
Blocks: 755739
(Reporter)

Comment 1

7 years ago
Jake - for tegra-204, can you also confirm it's PDU assignment?

inventory says 

pdu5.df202-1.build.mtv1.mozilla.com
pduid: .AA5

but the tegra isn't being cycled via pdu.

thanks
Assignee: server-ops-releng → mlarrain
colo-trip: --- → mtv1
Assignee: mlarrain → jwatkins
bear:  I manually cycled the power via the pdu web interface and confirmed tegra-204 is correctly associated with pdu5.df202-1.build.mtv1.mozilla.com pduid: .AA5

The reboot got it to a point where I could ping it but just for safe measure I flashed the nvram and formatted/reinitialized the sdcard.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Alias: tegra-recovery
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.