Closed Bug 449059 Opened 18 years ago Closed 18 years ago

Revive VMs after ESXHost crash

Categories

(Release Engineering :: General, defect, P1)

Product:
Release Engineering
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: joduinn, Assigned: joduinn)

Details

When bm-vmware05 crashed, it took down the following VMs: fx-linux-1.9-slave1 moz2-win32-slave06 prometheus-vm tb-linux-tbox try-master These all need to be revived.
Assignee: nobody → joduinn
Priority: -- → P1
fyi: The bm-vmware05 kernel panic is being worked on by IT in bug#448908.
fx-linux-1.9-slave1 moz2-win32-slave06 prometheus-vm tb-linux-tbox try-master ...were all still powered off, even though the host is back online again. I've now started the VMs, and will manually start up processes.
fx-linux-1.9-slave1 still has two drives on netapp-b which has had issues in the past. Not sure why this wasn't moved. I'd rather shutdown the VM and move it instead of chancing a storage vmotion. Figure 2-3 hours. When's a good time to do that?
(In reply to comment #3) > fx-linux-1.9-slave1 still has two drives on netapp-b which has had issues in > the past. Not sure why this wasn't moved. > > I'd rather shutdown the VM and move it instead of chancing a storage vmotion. > Figure 2-3 hours. > > When's a good time to do that? > Go for it. fx-linux-1.9-slave1 is already down, so now is as a good a time as any.
moz2-win32-slave06 now back alive and responding to pings from buildmaster.
prometheus-vm is now back. Thanks to nthomas for verifying that a simple reboot is enough - the updaters are running on prometheus-vm are triggered by cron, so nothing manual to do here! :-)
try-master is now back - thanks nthomas for doing that one!
fx-linux-1.9-slave1 is coming back online.
fx-linux-1.9-slave1 has had it's filesystem moved by mrz, and then nthomas walked me through restarting the processes on it as the doc was wrong. This is now back. tb-linux-tbox now back. All done.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.