ReleaseEngineering/How To/Decommission Slave: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
*** People from DCOps team must mark these machines as decommissioned | *** People from DCOps team must mark these machines as decommissioned | ||
** Remove from buildbot-configs | ** Remove from buildbot-configs | ||
*** mozilla-tests/production_config.py | *** mozilla-tests/production_config.py or mozilla/production_config.py | ||
** Remove from DB | ** Remove from DB | ||
= Usefull bug examples = | = Usefull bug examples = | ||
* Bug 1396454 | * Bug 1396454 | ||
Revision as of 12:13, 25 September 2017
There are a few steps that need to be followed here in order to decommission a slave.
The list of slaves in DB is available here (https://secure.pub.build.mozilla.org/slavealloc/ui/#slaves)
- In order to decommission a slave the bellow steps must be taken in this order:
- Disable slave from production
- Make sure is no longer attach to a master
- Remove from Nagios
- From puppet sysadmin repository (modules/nagios4/manifests/prod/releng/scl3.pp)
- Remove from Inventory
- People from DCOps team must mark these machines as decommissioned
- Remove from buildbot-configs
- mozilla-tests/production_config.py or mozilla/production_config.py
- Remove from DB
Usefull bug examples
- Bug 1396454