This is a tracking bug to decomm/power down hosts that are no longer in user and potentially creating audible alerts in the B28 thermocab.
I've powered down all unused/decommissioned hosts in this rack. There are still 5 hosts that actively serve Sync users, and the rest looks to be networking equipment. For any DCOps onsite for the next visit, can you let me know what is still alerting? Much appreciated!
Whiteboard: [unused hosts powered off, need dcops followup to see what else is alerting]
Assignee: server-ops-dcops → vle
colo-trip: --- → scl3
QA Contact: jbarnell
>There are still 5 hosts that actively serve Sync users, and the rest looks to be networking equipment. these are the 5 that i found on and ignored them, the others have been unplugged and are in the process of being unracked. wp-db42 wp-db46 wp-db50 wp-db6 wp-db59 only one i see reachable is wp-db42, intended? >can you let me know what is still alerting? only one left alerting, i think it's due to a bad drive perhaps? wp-db46
We should power off: wp-db42 wp-db59 I think wp-db6 might be wp-db60, but lets double check with the serial number (A1-16725)
yah 60 has been powered off and unracked - confirmed via serial number. i powered off 42 and 59, let me know if there are any alerts. the only remaining nodes in this Thermos are 46 (beeping one) and 6 (HP DL385G7), leaving 2 nodes. i'm planning a return trip next week 9/28 for the HSM servers and will unrack 42 and 59 to make sure we don't have any issues.
actually there's 3, sorry about that. there's also 50 which i've left alone. that leaves 3 nodes still in this rack: 6, 46, 50
this is complete. i've unracked the remaining nodes and left the 3 untouched as noted. phx1 exit spreadsheet updated.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
wp-db46 is still alerting, we're going to leave it as is as it'll be decommissioned when we exit. 6:49 PM <jlaz> its probably drive related, which i wouldnt be too surprised about 6:49 PM <jlaz> but yeah, we'll have to leave it alerting :|
You need to log in before you can comment on or make changes to this bug.