Closed Bug 487654 Opened 16 years ago Closed 16 years ago

reset ESX host bm-vmware02

Categories

(mozilla.org Graveyard :: Server Operations, task, P1)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: aravind)

References

Details

The new bm-vmware02 just died, taking down the VMs that were on it. From irc, mrz thinkgs this needs physical reset.
Severity: normal → blocker
Priority: -- → P1
Summary: reset bm-vmware02 → reset ES host bm-vmware02
Summary: reset ES host bm-vmware02 → ESX host bm-vmware02 hardware failure
The physical reset did not help, we are now bringing up the VMs on the other esx servers.
Assignee: server-ops → aravind
Summary: ESX host bm-vmware02 hardware failure → reset ES host bm-vmware02
Here is the list of VMs impacted. bm-l10n-win2k3-01 fx-win32-1.9-slave2 fxdbug-win32-tbox tb-linux-tbox moz2-linux-slave22 moz2-linux-slave24 production-prometheus-vm try-master fx-linux-1.9-slave1 fx-linux-1.9-slave2 moz2-linux-slave15 moz2-win32-slave24 moz2-win32-slave27
Assignee: aravind → server-ops
Summary: reset ES host bm-vmware02 → reset ESX host bm-vmware02
Working with vmware on re-attaching the VMs.
Assignee: server-ops → aravind
The following are back online: fxdbug-win32-tbox eql01-bm01 tb-linux-tbox eql01-bm02, netapp-c-001 moz2-linux-slave22 eql01-bm08 moz2-linux-slave24 eql01-bm08 try-master eql01-bm01 fx-linux-1.9-slave1 d-sata-build-001 fx-linux-1.9-slave2 eql01-bm02 moz2-linux-slave15 eql01-bm05 moz2-win32-slave24* eql01-bm07 moz2-win32-slave27 eql01-bm08 fx-win32-1.9-slave2 eql01-bm01
still working on the confusion over production-prometheus-vm.
production-prometheus-vm is online. Please reopen if there are any issues.
Status: NEW → RESOLVED
Closed: 16 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.