Closed
Bug 645145
Opened 13 years ago
Closed 13 years ago
please clone all remaining linux64-ix-slave machines from bug 644316 refimage
Categories
(Infrastructure & Operations :: RelOps: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhford, Assigned: shui)
References
Details
I was able to get these machines into staging with minimal fuss (buildbot.tac needed to have the hostname set, i needed to clean puppetca certs) Please image all remaining linux64-ix-slaveXX machines, except linux64-ix-slave01, bug644316#c3
Reporter | ||
Comment 2•13 years ago
|
||
Spencer, did you reimage linux64-ix-slave01?
Comment 3•13 years ago
|
||
(In reply to comment #2) > Spencer, did you reimage linux64-ix-slave01? Per irc, he did in fact image slave01.
Reporter | ||
Comment 4•13 years ago
|
||
Spencer, what is that status of these machines? Which machines have been finished so far?
Assignee | ||
Comment 5•13 years ago
|
||
linux64-ix-slave4 linux64-ix-slave10-13, out for repair linux64-ix-slave16 out for repair linux64-ix-slave26 has no hard drive linux64-ix-slave37 cant boot into network linux64-ix-slave40 out for repair linux64-ix-slave41 out for repair Following linux64-ix-slave could not be imaged the rest have been reimaged and have had host name changed
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•13 years ago
|
||
(In reply to comment #5) > linux64-ix-slave4 > linux64-ix-slave10-13, out for repair > linux64-ix-slave16 out for repair > linux64-ix-slave26 has no hard drive > linux64-ix-slave37 cant boot into network > linux64-ix-slave40 out for repair > linux64-ix-slave41 out for repair > > Following linux64-ix-slave could not be imaged the rest have been reimaged and > have had host name changed I take it that this is the list of machine that weren't imaged, does that mean that all slaves 01-39 not in this list are imaged and ready to go?
Status: RESOLVED → UNCONFIRMED
Ever confirmed: false
Resolution: FIXED → ---
Reporter | ||
Comment 7•13 years ago
|
||
wth, bugzilla!
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Comment 8•13 years ago
|
||
linux64-ix-slave37 is fine, I'm imaging it now. It was tricky to catch in the BIOS screen, but I got it.
Comment 9•13 years ago
|
||
slave26 is another bad drive for the pile.
Updated•11 years ago
|
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•