Currently on loan in bug 749637.

(resolving to get it off buildduty radar for now)

(In reply to Justin Wood (:Callek) from comment #2) > (resolving to get it off buildduty radar for now) According to :decoder this is *actually* bad. Adding to tegra-recovery, we need the PDU labeling verified (we currently have it allocated to PDU at pdu5.df202-1.build.mtv1.mozilla.com and ID .AA5) It is exhibiting as "hung" and PDU not powercycling it. So to be clear, [for IT] we need: * Reimage/flash-sdcard * Verify PDU info on our end is currently correct * Run a PDU based reboot cycle before leaving colo to verify. Thanks

This tegra has been re-imaged/flashed and reinitialized. I have also verified that the pdu info is correct and have tested it with a PDU based reboot which was visually confirmed.

Confirmed, it's working now. Thanks! :)

This is still on loan, possibly semi-permanently.

Might want to do something about the nagios check, then.

(In reply to Phil Ringnalda (:philor) from comment #7) > Might want to do something about the nagios check, then. I disabled notifications for these checks, as they're still loaned out afaict.

Still a sec-team loaner, but needs a reimage

I don't know what to do with this bug. Should we add a date to the whiteboard saying "Do not ask before DATE"? I don't see an open dependency for the loan.

This is not needed by decoder anymore. We need to bring it back into production if we can.

ping check failing; recovery didn't help

formatted, flashed and reimaged. [vle@admin1a.private.scl3 ~]$ telnet tegra-204.tegra.releng.scl3.mozilla.com 20701 Trying 10.26.85.157... Connected to tegra-204.tegra.releng.scl3.mozilla.com. Escape character is '^]'. $>^]q

this was added back to devices.json but still not being picked up or taking jobs. closing bug 999930 as the role of that bug, putting tegras out of loan pool and back into prod, is complete.

created the tegra- folder on foopy125, as per devices.json.