ReleaseEngineering/How To/Request That a Machine Be Reimaged

Slave class specific instructions

So ... off the bat ... RelEng can perform reimages directly. Please only raise a bug to ask RelOps to do it, if the following instructions are not sufficient enough. And in that case, please ask Rel Ops the procedure, so we can update this doc.

Windows

https://mana.mozilla.org/wiki/display/DC/How+To+Reimage+Releng+iX+Windows+Machines

Mac

https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=34014655

Linux

https://mana.mozilla.org/wiki/display/DC/How+To+Reimage+Releng+iX+and+HP+Linux+Machines for linux

Pandas

https://wiki.mozilla.org/ReleaseEngineering/Mozpool/How_To_Use_the_Mozpool_Web_UI#re-image_a_device_I.27ve_already_requested

Other / if all else fails

If all else fails, and the above instructions do not help you:

• File a bug to reimage the machine, mark it as blocking the slave's problem tracking bug.
• If a releng bug doesn't already exist for the slave, file a new one to bring the slave back into production, e.g., 'set up re-imaged slave talos-r3-slave99'. Make the server operations bug block the releng bug.
• Add the slave to the slave tracking spreadsheet with a link to the appropriate bug.

Post Imaging Steps

• Check PostImage on what IT should be doing after imaging to verify it got done.
• Follow the instructions on how to set up a freshly imaged slave.