Closed Bug 432408 Opened 17 years ago Closed 17 years ago

reimage xserve16

Categories

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

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: phong)

References

Details

Can you please reimage bm-xserve16 so it is identical to bm-xserve17 and bm-xserve18? I confirm there is nothing on bm-xserve16 to be preserved, so you can start re-imaging whenever suits. (Not sure if you have a clone on disk already available that you can use, or if you need to schedule bm-xserve17/bm-xserve18 downtime before you can do this.)
Assignee: server-ops → phong.tran
Flags: colo-trip+
I can do this tonight if you want to schedule downtown for tonight.
Status: NEW → ASSIGNED
John, Is 7 or 8 PM tonight a good time to take either bm-xserve17 or bm-xserve18 down to take any image? Let me know and I can take care of this tonight.
Phong; we cant take down bm-xserve17, bm-xserve18 just now. Do you still have the image used to create bm-xserve17, bm-xserve18? Could we use that for imaging bm-xserve16 instead of having to take down the live machines?
It looks like bm-xserve17 was built with an image from bm-xserve16 as reference in bug 421923. I'll see if I can find that image and use that to restore.
bm-xserve16 has been reimaged with image taken on 3/10/2008.
Wasn't this image taken from bm-xserve16?
That's the same image we used for 17 and 18.
Phong; In comment#5 are you saying that you've just reimaged bm-xserve16? In which case, can we now just close this bug or did I mis-understand?
John, That is correct. I restored bm-xserve16 from an old image of bm-xserve16 taken back in March.
Status: ASSIGNED → RESOLVED
Closed: 17 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.