Move try slaves out of sandbox and into build network

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
--
major
RESOLVED FIXED
8 years ago
3 years ago

People

(Reporter: lsblakk, Assigned: jabba)

Tracking

Details

Please move try-w32-slave20 (10.2.76.173) out of the sandbox and into the build network.
(Reporter)

Comment 1

8 years ago
Also move try-linux-slave08 and try-mac-slave13 into build.
OS: Windows Server 2003 → All
Summary: Move try-w32-slave20 into build network → Move try slaves out of sandbox and into build network
(Reporter)

Updated

8 years ago
Severity: normal → major

Updated

8 years ago
Assignee: server-ops → jdow
Flags: colo-trip+

Comment 2

8 years ago
is there any else that needs to be done other than updating dns and moving the ports over to the buld vlan?
(Reporter)

Comment 3

8 years ago
actually, yes.  in fact these will need to be re-imaged with their respective ref-images since they are in the sandbox and not guaranteed to be safe.  we should start with clean images in the build network.
(Reporter)

Comment 4

8 years ago
Eta on this?

Comment 5

8 years ago
try-win32-slave20 and try-linux-slave08 are both VMs.  Can I delete these now?
(Reporter)

Comment 6

8 years ago
delete them and recreate them again with the same names, but in the build network? - yes

Comment 7

8 years ago
try-w32-slave20.build.m.o    10.2.90.170
try-linux-slave08.build.m.o  10.2.90.171
(Assignee)

Comment 8

8 years ago
try-mac-slave13.build.m.o 10.2.90.173
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.