Closed
Bug 481805
Opened 16 years ago
Closed 16 years ago
Please reimage bm-xserve12
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: phong)
References
Details
Please reimage bm-xserve12; you should use bm-xserve22 as the master to image *from*.
Reporter | ||
Comment 1•16 years ago
|
||
phong: heads up, nthomas just reminded me that this machine is an older intel-based xserve. Hope you can image this anyway, but let us know if you hit problems, ok?
Assignee | ||
Updated•16 years ago
|
Assignee: server-ops → phong
Assignee | ||
Comment 2•16 years ago
|
||
I'll see if I have an image of bm-xserve22 as a ref image. If not, I will have to take it down to make an image first.
Assignee | ||
Updated•16 years ago
|
Flags: colo-trip+
Assignee | ||
Comment 3•16 years ago
|
||
It was imaged from bm-xserve16. I am using that as the ref image.
Assignee | ||
Comment 4•16 years ago
|
||
re-imaged.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•16 years ago
|
||
(In reply to comment #5)
> Please reimage bm-xserve12; you should use bm-xserve22 as the master to image
> *from*.
(In reply to comment #3)
> It was imaged from bm-xserve16. I am using that as the ref image.
Phong; curious why you used bm-xserve16, not bm-xserve22. Was there any problems imaging from bm-xserve22? Or was bm-xserve16 physically more convenient?
(Asking because we've had cloning problems before with xserves, so curious for backstory...)
Assignee | ||
Comment 6•16 years ago
|
||
bm-xserve22 was deployed from an existing image of bm-xserve16. I can take an image of bm-xserve22, but that would require downtime. I didn't get confirmation that I can take down bm-xserve22 to make an image. I can still do this if that's preferable for you.
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•