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

From MozillaWiki
Jump to navigation Jump to search
(Created page with "First, file a new bug in the 'Server Operations: RelEng' component, giving the name of the host in the summary, e.g., 'please reimage talos-r3-slave99'. If a releng bug doesn't ...")
 
(Updated the "Open Bug Link" as it seemed that product doesn't exist anymore.)
 
(8 intermediate revisions by 6 users not shown)
Line 1: Line 1:
First, file a new bug in the 'Server Operations: RelEng' component, giving the name of the host in the summary, e.g., 'please reimage talos-r3-slave99'.
{{Release Engineering How To|Request That a Machine Be Reimaged}}


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.
== Slave class specific instructions ==


Add the slave to the slave tracking spreadsheet with a link to the appropriate bug.
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
 
=== 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?product=Infrastructure%20%26%20Operations&component=DCOps&short_desc=please%20reimage%20SLAVE File a bug to reimage the machine], mark it as blocking the slave's problem tracking 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)
* finally, re-enable it in slavealloc and reboot it.

Latest revision as of 23:19, 3 March 2018


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

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
  • File a bug to reimage the machine, mark it as blocking the slave's problem tracking 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)
  • finally, re-enable it in slavealloc and reboot it.
Retrieved from "https://wiki.mozilla.org/index.php?title=ReleaseEngineering/How_To/Request_That_a_Machine_Be_Reimaged&oldid=1189681"