Closed Bug 770519 Opened 12 years ago Closed 12 years ago

tegra recovery

Categories

(Infrastructure & Operations :: DCOps, task)

Product:
Infrastructure & Operations
Component:
DCOps
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: van)

References

Details

(Whiteboard: mtv1) 

Both tegra-218 and 280 refuse to respond to a PDU reboot, need some manual poking methinks.
Blocks: tegra-171
Assignee: server-ops-releng → jwatkins
colo-trip: --- → mtv1
Depends on: tegra-073
Blocks: tegra-073
No longer depends on: tegra-073
Blocks: tegra-154
Blocks: tegra-049
Going to assign this to van so he and jake can work on this together.
Assignee: jwatkins → vle
Component: Server Operations: RelEng → Server Operations: DCOps
QA Contact: arich → dmoore
Whiteboard: mtv1
Tegra-218 and Tegra-280 had the dip switch in the batt position, switched to norm and both Tegras are back online.

Reimaged Tegras-[171,154,073] and those are all back online.

We were unable to bring back Tegra-049, I have updated my findings in the blocker ticket.

Inventory was also updated with the oob ips of the Tegras(if they were missing).

Regards,
Van
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Alias: tegra-recovery
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.