We're not sure what's going on with this slave, but it has killed a bunch of reconfigs by hanging in various weird ways. Let's try re-imaging it, and if that doesn't work, we'll just decommission the hardware.
The slave has been reimaged. Over to releng for puppetization and configuration.
Assignee: mlarrain → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
And it's back down again. I'm guessing this is another dead machine.
Assignee: nobody → mlarrain
Component: Release Engineering → Server Operations: RelEng
QA Contact: release → zandr
Summary: please reimage try-mac-slave35 → decommission try-mac-slave35
OK. I will remove from our configs as well.
Removed machine from data center. Will give to Desktop to decom.
Assignee: mlarrain → hlangi
Status: NEW → ASSIGNED
Component: Server Operations: RelEng → Server Operations: Desktop Issues
QA Contact: zandr → tfairfield
Can we please double check that this slave has been removed from dns/nagios/inventory? armenzg-laptop $ host try-mac-slave35 try-mac-slave35.build.mozilla.org is an alias for try-mac-slave35.build.sjc1.mozilla.com. try-mac-slave35.build.sjc1.mozilla.com has address 10.2.91.105
No need to double-check - it hasn't been removed yet, but it will be.
Has this been removed from Nagios, DHCP, DNS and inventory?
Closing this out. Hard Drive has been wiped.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.