Closed Bug 432502 Opened 16 years ago Closed 16 years ago

qm-centos5-03 - migrate to bm-vmware03

Categories

(Release Engineering :: General, defect, P3)

Product:
Release Engineering
Component:
General
Platform:
All
Other
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mrz, Assigned: mrz)

References

Details

Tracking to migrate VM to HA ESX enviro.  Need tree closure and window.
Assignee: server-ops → nobody
Component: Server Operations → Release Engineering
QA Contact: justin → release
Whiteboard: need-downtime-window
Assignee: nobody → mrz
Blocks: 432374
Whiteboard: need-downtime-window → blocked on rc1
Priority: -- → P3
Whiteboard: blocked on rc1 → needs scheduled downtime
Is this (and the other two) blocked on RC1 or can it be scheduled for any downtime window?
(In reply to comment #1)
> Is this (and the other two) blocked on RC1 or can it be scheduled for any
> downtime window?

This is a tier 1 unit test machine, so I guess blocked on RC1. :/
Blocks: 432944
No longer blocks: 432944
(In reply to comment #2)
> (In reply to comment #1)
> > Is this (and the other two) blocked on RC1 or can it be scheduled for any
> > downtime window?
> 
> This is a tier 1 unit test machine, so I guess blocked on RC1. :/
> 
Yep, cannot take this down until after rc1 is produced (!= rc1 shipped). 

We're currently planning to have a scheduled downtime *after* we hand the RC1 builds to QA, and *before* we reopen the tree. Likely during the afternoon Monday if current predictions hold true, but stay tuned...
Whiteboard: needs scheduled downtime → blocked on RC1/needs downtime
We're still doing the win32 builds, but dont need this any more. Its now ok to take down.
Whiteboard: blocked on RC1/needs downtime
Moved.
Status: NEW → RESOLVED
Closed: 16 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.