ReleaseEngineering/How To/Request That a Machine Be Reimaged: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Release Engineering How To|Request That a Machine Be Reimaged}} | {{Release Engineering 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 | |||
Follow the instructions on how to [[ReleaseEngineering/How_To/Set_Up_a_Freshly_Imaged_Slave | set up a freshly imaged slave]]. | === 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 | |||
=== Tegras === | |||
Whaaaaat? Get that thing away from me. Joking apart - tegras are being decommissioned - we should only be retiring tegras now, not reimaging them. | |||
=== Other / if all else fails === | |||
If all else fails, and the above instructions do not help you: | |||
* [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. | |||
* 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 [[ReleaseEngineering/How_To/Set_Up_a_Freshly_Imaged_Slave | set up a freshly imaged slave]]. | |||
Revision as of 13:34, 31 July 2014
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
Tegras
Whaaaaat? Get that thing away from me. Joking apart - tegras are being decommissioned - we should only be retiring tegras now, not reimaging them.
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.