Replace or reimage tb2-darwin10-slave66

RESOLVED FIXED

Status

Infrastructure & Operations
RelOps
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: jhopkins, Assigned: arr)

Tracking

Details

(Reporter)

Description

6 years ago
tb2-darwin10-slave66 has become unreliable, failing to work properly the past two colo trips.

I recommend we replace it with one of the OS X 10.6 minis sent from Vancouver (mini64-xx).
(Assignee)

Updated

6 years ago
colo-trip: --- → sjc1
(In reply to John Hopkins (:jhopkins) from comment #1)
> tb2-darwin10-slave66 has become unreliable, failing to work properly the
> past two colo trips.
was it just rebooted, or completely reimaged in previous trips? 



> I recommend we replace it with one of the OS X 10.6 minis sent from
> Vancouver (mini64-xx).
I agree, so long as mini64-xx is identical spec to the other 10.6 minis in the pool, right? (its worth being careful about this given the plan-of-record to consolidate the two separate pools of machines into one larger pool of machines, where its important that the one larger pool is of identical machines.)
(Reporter)

Comment 2

6 years ago
> was it just rebooted, or completely reimaged in previous trips? 

It was rebooted each trip.  However, the system was only imaged a few weeks ago.

> I agree, so long as mini64-xx is identical spec to the other 10.6 minis in the pool, right?

In terms of builds, this system can be safely used in the Thunderbird pool.  If IT/Relops have additional requirements they'll need to chime in.  However, for now I think it makes more sense to get that replacement mini online as we're down 1 build slave in a small pool.

Comment 3

6 years ago
Talking with jhopkins last week, this machine is 1 of 6 providing darwin10 coverage. jhopkins was going to look into wait times to make sure we were still keeping up with only 5 builders.

If the wait times are fine with 5 machines, I would suggest bringing it back from sjc1 for diagnosis.

What rev is this mini? Could it be re-deployed into the releng pool if it can be resurrected? The long-term goal is to get Thunderbird building on the releng infra anyway (bug 698843).
(Reporter)

Comment 4

6 years ago
Wait times here:

 http://build.mozillamessaging.com/buildbot/production/pending/
(Assignee)

Comment 5

6 years ago
I rebooted the machine and it seemed to come back up fine.  jhopkins was going to turn off ARD to see if that helped the issue.
Assignee: server-ops-releng → arich
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.