Re-image 24 bld-linux64-ix machines as win64 builders

RESOLVED FIXED

Status

task
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: armenzg, Assigned: arich)

Tracking

Details

I've disabled all of these slaves and gracefully shut down them.
Please do not re-image them until 3 hours have passed from the time of filing this bug.

How can I disable the nagios check for them?

Many thanks.

From try, 11 of them:
bld-linux64-ix-038
bld-linux64-ix-039
bld-linux64-ix-040
bld-linux64-ix-041
bld-linux64-ix-042
bld-linux64-ix-043
bld-linux64-ix-044
bld-linux64-ix-045
bld-linux64-ix-046
bld-linux64-ix-047
bld-linux64-ix-048
bld-linux64-ix-049
bld-linux64-ix-050

From build, 13 of them:
bld-linux64-ix-004
bld-linux64-ix-015
bld-linux64-ix-016
bld-linux64-ix-017
bld-linux64-ix-018
bld-linux64-ix-019
bld-linux64-ix-020
bld-linux64-ix-021
bld-linux64-ix-022
bld-linux64-ix-023
bld-linux64-ix-024
bld-linux64-ix-025
bld-linux64-ix-026


The new names should be:
w64-ix-slave134
w64-ix-slave135
w64-ix-slave136
w64-ix-slave137
w64-ix-slave138
w64-ix-slave139
w64-ix-slave140
w64-ix-slave141
w64-ix-slave142
w64-ix-slave143
w64-ix-slave144
w64-ix-slave145
w64-ix-slave146
w64-ix-slave147
w64-ix-slave148
w64-ix-slave149
w64-ix-slave150
w64-ix-slave151
w64-ix-slave152
w64-ix-slave153
w64-ix-slave154
w64-ix-slave155
w64-ix-slave156
w64-ix-slave157
These are going to require a bunch of back end infrastructure (vlan, dns, dhcp, nagios) changes, so we probably won't get to these till next week.
Assignee: relops → qfortier
Assignee: qfortier → arich
Okay, getting back to this, you say you're repurposing 24 total, 11 from try, but you list 13 machines there (26 total).  Which should actually be repurposed?
Flags: needinfo?(armenzg)
(In reply to Amy Rich [:arich] [:arr] from comment #2)
> Okay, getting back to this, you say you're repurposing 24 total, 11 from
> try, but you list 13 machines there (26 total).  Which should actually be
> repurposed?

Sorry about that. You can skip 49 & 50. I will update slavealloc's note.
Flags: needinfo?(armenzg)
Depends on: 902096
The following machines have been reimaged:

w64-ix-slave135
w64-ix-slave136
w64-ix-slave137
w64-ix-slave138
w64-ix-slave139
w64-ix-slave140
w64-ix-slave141
w64-ix-slave142
w64-ix-slave143
w64-ix-slave145
w64-ix-slave146
w64-ix-slave147
w64-ix-slave148
w64-ix-slave149
w64-ix-slave150
w64-ix-slave151
w64-ix-slave152
w64-ix-slave153
w64-ix-slave154
w64-ix-slave155
w64-ix-slave156
w64-ix-slave157


These two are waiting for hands on by dcops:

w64-ix-slave134
w64-ix-slave144
This caused
Wed 08:20:37 PDT [4574] nagios1.private.releng.scl3.mozilla.com:scl1-bld-linux64-ix-ping cluster is UNKNOWN: Could not parse arguments (http://m.allizom.org/scl1-bld-linux64-ix-ping+cluster)

:arr can you drop the cluster check entirely when you get a chance? (ashish claims the alert happens because we removed all hosts from the cluster, I believe him)
Flags: needinfo?(arich)
cluster check removed, and the last couple hosts reimaged according to sub-bug.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(arich)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.