ReleaseEngineering/How To/Request That a Machine Be Reimaged: Difference between revisions
< ReleaseEngineering | How To
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 ...") |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Release Engineering How To}} | |||
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'. | 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'. | ||
Revision as of 22:29, 26 January 2011
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 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.