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}} | ||
First, | First, [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. | 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. | ||
Revision as of 17:26, 12 July 2013
First, 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.
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.