Closed Bug 650297 Opened 13 years ago Closed 13 years ago

Remove try-mac-slave35 from our configs and slavealloc

Categories

(Release Engineering :: General, defect, P4)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 700705

People

(Reporter: catlee, Assigned: armenzg)

References

Details

(Whiteboard: [slaveduty])

Attachments

(1 file)

It hung another reconfig on pm02-try
Is it possible that there's some state on the master that's killing this, or has the master been restarted in the interim?
(In reply to comment #1)
> Is it possible that there's some state on the master that's killing this, or
> has the master been restarted in the interim?

The master has been restarted several times to work around this slave
Attachment #526283 - Flags: review?(dustin)
Attachment #526283 - Flags: review?(dustin) → review+
Comment on attachment 526283 [details] [diff] [review]
remove try-mac-slave35 from configs

http://hg.mozilla.org/build/buildbot-configs/rev/2d7fcc8eb4e4
Attachment #526283 - Flags: checked-in+
Whiteboard: [slaveduty]
It looks like this is fixed.  Checked a try master to verify
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
How is this fixed?  Has the slave already been reimaged?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #5)
> It looks like this is fixed.  Checked a try master to verify

Shut down the slave ASAP por favor.
A shutdown slave is a waste of resources - this needs to get driven to an actual resolution, but I'm not sure what the current state is..
(In reply to comment #8)
> A shutdown slave is a waste of resources - this needs to get driven to an
> actual resolution, but I'm not sure what the current state is..

I want it shut down now to avoid the slave hanging again.  This machine needs inspection before hooking up again to production or staging.
OK, from the looks of it, it is shut down.  It's also disabled in slavealloc.  I filed bug 650842 to re-image it.  We can bring it up in preproduction at that point, and see what it does.
Priority: -- → P4
This slave popped back up today and started trying to login to bm09. I've disabled it in slavealloc until bug 650842 happens.
Curious that it had been re-enabled..
(In reply to Dustin J. Mitchell [:dustin] from comment #12)
> Curious that it had been re-enabled..

Yeah. :/

There was no note with the bug # in slavealloc (or if there was, it was cleared), so I added one back.
This slave is being decommissioned by IT in bug 650842.

I will make sure we remove it from slavealloc as well.
Assignee: nobody → armenzg
Summary: Deploy nuclear option on try-mac-slave35.build.mozilla.org → Remove try-mac-slave35 from our configs and slavealloc
To help me track removal of slaves I'm going to be doing all of it in bug 700705.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: