We should do this batch with the *new* image (as of this writing it is on the imaging netbooks with 'STAGING' instead of 'PRODUCTION'

Callek, These are the results of the tegra upgrades, after doing a complete audit across all our foopies. Please note some of these tegras may not be "production" but instead assigned to private test masters, loaned out to people, in staging, or something else. I'm off on PTO now - would I be able to leave you with this list, and you work out which ones should be reimaged? Thanks buddy! Pete See --> https://bugzilla.mozilla.org/show_bug.cgi?id=914302#c45

Please note, when bug 869779 lands - it will be possible to generate a report like above (https://bugzilla.mozilla.org/show_bug.cgi?id=914302#c45) at any time, using the foopy fabric scripts...

All tegra has been re-imaged except the following 3. 202 203 269 Went to Stally in SF. We were not able to find 202 & 203 boards. We will look for them tomorrow.

(In reply to John Pech [:jpech-lbc] from comment #3) > All tegra has been re-imaged except the following 3. > > 202 > 203 These were previous perpetual loaners by sec-team, but they should have still been homed with the rest of our devices. attached to pdu2.df201-4.build.mtv1.mozilla.com > 269 Went to Stally in SF. Huh who authorized that, and/or where was it documented. We "loaned" that device to Shane Tully but also loaned a foopy and expected it to be kept in its home afaict. (if my memory is wrong and there is a bug that says it moved with releng signoff, I apologize, but I want to get track of it since he says he is done with it)

Tegra-202 & Tegra-203 has been found and re-imaged.

Comment on attachment 807903 [details] A note of location for Tegra-269 Ahh that note was left by ctalbert. whom reminds me that *I* told him it was ok to move. He has it now and will bring it back on monday, at which point I'll have DCOps handle it in a seperate recovery bug. Thanks!