Closed Bug 494315 Opened 16 years ago Closed 16 years ago

Reimage and rename old 1.66GHz mac minis

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: phong)

Details

Turns out the following machines were 1.66GHz, not 1.83GHZ as expected, which means they cannot be used in main pool-of-talos-slaves. Also, they should not be called "rev2". Please reimage these machines with the "old" Talos ref-image for these o.s., and rename these machines as follows: talos-rev2-xp05 -> talos-rev1-xp01 talos-rev2-xp06 -> talos-rev1-xp02 talos-rev2-xp07 -> talos-rev1-xp03 talos-rev2-xp08 -> talos-rev1-xp04 talos-rev2-vista05 -> talos-rev1-vista01 talos-rev2-vista06 -> talos-rev1-vista02 talos-rev2-vista07 -> talos-rev1-vista03 talos-rev2-vista08 -> talos-rev1-vista04 talos-rev2-linux03 -> talos-rev1-linux01 talos-rev2-linux04 -> talos-rev1-linux02 talos-rev2-linux05 -> talos-rev1-linux03 talos-rev2-linux06 -> talos-rev1-linux04 talos-rev2-tiger03 -> talos-rev1-tiger01 talos-rev2-tiger04 -> talos-rev1-tiger02 talos-rev2-tiger05 -> talos-rev1-tiger03 talos-rev2-tiger06 -> talos-rev1-tiger04 This rename will also mean changes to nagios, inventory and DNS for all of these machines. As these are all now in staging, you can start this whenever you have time. (Sorry for the extra work, we really didnt expect these to be 1.66GHz, and are scrambling elsewhere to cleanup data.)
Do we really need to re-image these with the old Talos Image? They were never re-image with the new image to begin with?
Assignee: server-ops → phong
(In reply to comment #1) > Do we really need to re-image these with the old Talos Image? They were never > re-image with the new image to begin with? I know these were not reimaged today. However, while working on these during today's downtime, we found differences of what software is installed on these machines. Reimaging with the old talos image is easiest/best way to guarantee each machine for a given o.s. is truly identical.
dns updated.
can these be re-imaged now?
talos-rev1-tiger02, and talos-rev1-linux02 are ready.
talos-rev1-tiger01, talos-rev1-linux03/04 are ready.
talos-rev1-tiger03/04 are ready.
I think there's an error with one of the vista machines, I don't see talos-rev1-vista03, but I see two vista02 slaves. talos-rev1-vista02.mozilla.org A 10.2.73.47 talos-rev1-vista02.mozilla.org A 10.2.73.48
I haven't re-imaged any of the vista minis yet.
I think it's the DNS that's messed up right now.
dns corrected.
What's left here? Re-imaging the bulk of that list still? Are we gated on you giving the okay?
(In reply to comment #12) > What's left here? Re-imaging the bulk of that list still? Are we gated on you > giving the okay? Some are already reimaged, but the rest still need to be reimaged. Wasnt aware of needing to give an okay for the remainder machines, but "okay". :-)
Phong, you have an ETA on these?
the rest have been re-imaged with the old image.
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.