ReleaseEngineering/How To/Request That a Machine Be Reimaged: Difference between revisions

ReleaseEngineering/How To/Request That a Machine Be Reimaged (view source)

444 bytes removed , 24 November 2017

Updated instructions on how to request a re-image for a HW machine

148

edits

@@ Line 13: / Line 13: @@
 === 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:
+* make sure the slave is disabled in slavealloc
 * [https://bugzilla.mozilla.org/enter_bug.cgi?component=Server%20Operations:%20DCOps&product=mozilla.org&short_desc=please%20reimage%20SLAVE 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.
+* after being re-imaged, do another check to make sure the machine is in a good shape (e.g it's accessible, has a proper resolution, etc)
-* Add the slave to the slave tracking spreadsheet with a link to the appropriate bug.
+* finally, re-enable it in slavealloc and reboot it.
-== Post Imaging Steps ==
-* Check [[PostImage]] on what IT should be doing after imaging to verify it got done.
-* Follow the instructions on how to [[ReleaseEngineering/How_To/Set_Up_a_Freshly_Imaged_Slave | set up a freshly imaged slave]].