ReleaseEngineering/How To/Send a Machine For Repair

< ReleaseEngineering‎ | How To
Revision as of 01:35, 13 May 2011 by Djmitche (talk | contribs) (Created page with "{{Release Engineering How To|Send a Machine For Repair}} = General = Machines slated for repair should first be cleaned of secret information - see [https://intranet.mozilla.org/...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

General

Machines slated for repair should first be cleaned of secret information - see How To/Clean A Slave For Shipment Externally (auth required).

In case the machine arrives back with its drive intact, any undesirable startup behaviors should be disabled. For slaves, this means disabling the slave in slavealloc. For masters, it means disabling the service.

Once everything is ready, shut the host down - Ops is much more confident un-racking a host that doesn't have spinning fans. Provide Ops with a clear description of the host - hostname and asset tag, if possible - for un-racking and preparation for shipping.