|Resolved||None||T176243 Decommission database hosts <= db2031 (tracking)|
|Resolved||RobH||T175685 Decommission db2010 and move m1 codfw to db2078|
|Resolved||RobH||T184090 Decommission db2016, db2017, db2018, db2019, db2023, db2028, db2029|
|Resolved||jcrespo||T183470 Setup newer machines and replace all old misc (m*) and x1 codfw machines|
|Resolved||Papaul||T187543 Decommission db2012|
|Resolved||Marostegui||T187722 Replace db2030 from m5 with another host (WAS: Degraded RAID on db2030)|
|Resolved||RobH||T187768 Decommission db2030|
|Resolved||RobH||T187886 Decommission db2011|
|Resolved||Request||None||T221424 decommission db2014,db2020, db2021, db2022, db2024, db2031|
@RobH @Papaul From our point of view, all hosts from db2001 to db2032 have been either decommissioned, scheduled for decommission or renamed/never existed. Can you check on your end that is true, and that there is no host in a limbo state?
Once we agree on this- I will close the ticket (but leave alone the open decommission tasks, as they may be pending).