elastic1017 is showing up as failing in all fleetwide Cumin/debdeploy runs, turning T230518 into a proper decommission ticket.

The first 5 steps should be completed by the service owner that is returning the server to DC-ops (for reclaim to spare or decommissioning, dependent on server configuration and age.)

Steps for service owner:

• - all system services confirmed offline from production use
• - set all icinga checks to maint mode/disabled while reclaim/decommmission takes place.
• - remove system from all lvs/pybal active configuration
• - any service group puppet/hiera/dsh config removed
• - remove site.pp, replace with role(spare::system)
• - unassign service owner from this task, check off completed steps,

Steps for DC-Ops:

The following steps cannot be interrupted, as it will leave the system in an unfinished state.

Start non-interrupt steps:

• - disable puppet on host (hardware is broken)
• - power down host (hardware is broken)
• - update netbox status to Decomissioning
• - disable switch port
• - switch port assignment noted on this task (for later removal)
• - remove all remaining puppet references (include role::spare)
• - remove production dns entries
• - puppet node clean, puppet node deactivate (handled by wmf-decommission-host)
• - remove dbmonitor entries on neodymium/sarin: sudo curl -X DELETE https://debmonitor.discovery.wmnet/hosts/${HOST_FQDN} --cert /etc/debmonitor/ssl/cert.pem --key /etc/debmonitor/ssl/server.key (handled by wmf-decommission-host)

End non-interrupt steps.

• - system disks wiped (by onsite)
• - IF DECOM: system unracked and decommissioned (by onsite), update racktables with result
• - IF DECOM: switch port configration removed from switch once system is unracked.
• - IF DECOM: add system to decommission tracking google sheet
• - IF DECOM: mgmt dns entries removed.
• - IF RECLAIM: system added back to spares tracking (by onsite)