Confirmed users
67
edits
No edit summary |
(Updated the "Open Bug Link" as it seemed that product doesn't exist anymore.) |
||
| (7 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{Release Engineering How To}} | {{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 | |||
=== 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. | |||