Bring up all new SeaMonkey Win32 VMs

RESOLVED FIXED

Status

SeaMonkey
Release Engineering
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: ewong, Assigned: ewong)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

6 years ago
Bug 764693 physically brought up all the SeaMonkey VMs into 
running order.  This bug is the SeaMonkey-Releng part which
brings these VMs into buildbot production.

Needed to do:
Action Items for SeaMonkey-Releng (ewong/callek):
 * For EACH slave
 **    Put back .ssh keys/known_hosts/etc. on all 4 VMs
 **    Enter correct slave password, and hostname into E:\builds\slave\buildbot.tac.bak and rename to buildbot.tac
 **    Verify hostname & domain of slave is correct
 **    test ssh connection to: stage, symbolpush, aus2
 **    Double check IP address (and hostmask) is set properly
 **    Restart VM
 * Verify in buildbot UI that the VM's connected and have started taking jobs
 * Monitor through to thursday, midday that jobs are good.
 * If they are (on cb-seamonkey-win32-*)
 **    Disable/delete buildbot.tac on and await jobs to finish.
 **    Delete .ssh directories from all users
 **    Delete temp files from all users
 **    Power Off these hosts
 **    Note here, or file a new bug (depending on if this bug is closed) that IT can delete these slaves.
(Assignee)

Updated

6 years ago
Depends on: 764693
(Assignee)

Comment 1

6 years ago
Both sea-vm-win32-1 and sea-vm-win32-2 are up and running builds.
(Assignee)

Updated

6 years ago
Version: SeaMonkey 2.9 Branch → unspecified
(Assignee)

Comment 2

6 years ago
Now sea-vm-win32-3 and sea-vm-win32-4 are up.
(Assignee)

Comment 3

6 years ago
All four VMs are up and running.  Closing this bug.
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

6 years ago
Blocks: 768303
You need to log in before you can comment on or make changes to this bug.