800079 - kickstart new foopies and imaging servers

Status: RESOLVED FIXED

(Infrastructure & Operations :: RelOps: General, task)

Description

[Amy Rich [:arr] [:arich]]

Kickstart the new foopies and imaging servers for the mobile expansion in scl1.

Comment 1

[Amy Rich [:arr] [:arich]]

We need to tighten down the flows next week, but for now the first rack of servers is complete.

mobile-imaging-001.p1.releng.scl1.mozilla.com
foopy39.p1.releng.scl1.mozilla.com
foopy40.p1.releng.scl1.mozilla.com
foopy41.p1.releng.scl1.mozilla.com
foopy42.p1.releng.scl1.mozilla.com
foopy43.p1.releng.scl1.mozilla.com
foopy44.p1.releng.scl1.mozilla.com
foopy45.p1.releng.scl1.mozilla.com

Waiting on more machines to be cabled to continue kickstart work.

Comment 2

[Amy Rich [:arr] [:arich]]

These have also been kickstarted:

foopy49.p2.releng.scl1.mozilla.com
foopy50.p2.releng.scl1.mozilla.com
foopy51.p2.releng.scl1.mozilla.com
foopy52.p2.releng.scl1.mozilla.com

mobile-imaging-005.p5.releng.scl1.mozilla.com
foopy67.p5.releng.scl1.mozilla.com
foopy68.p5.releng.scl1.mozilla.com
foopy69.p5.releng.scl1.mozilla.com
foopy70.p5.releng.scl1.mozilla.com
foopy71.p5.releng.scl1.mozilla.com
foopy72.p5.releng.scl1.mozilla.com
foopy73.p5.releng.scl1.mozilla.com

And these have been kickstarted but I suspect that the the boot order is wrong because they aren't booting from disk, so that needs to be fixed (bug 806030)

mobile-imaging-002.p2.releng.scl1.mozilla.com
foopy46.p2.releng.scl1.mozilla.com
foopy47.p2.releng.scl1.mozilla.com
foopy48.p2.releng.scl1.mozilla.com

Once they're rebooted, they should also come up and puppetize.

Waiting for the PDU swap in racks 3 and 4 before I can kickstart those machines.

Comment 3

[Amy Rich [:arr] [:arich]]

and

mobile-imaging-003.p3.releng.scl1.mozilla.com
foopy53.p3.releng.scl1.mozilla.com
foopy54.p3.releng.scl1.mozilla.com
foopy55.p3.releng.scl1.mozilla.com

foopy57.p3.releng.scl1.mozilla.com
foopy58.p3.releng.scl1.mozilla.com
foopy59.p3.releng.scl1.mozilla.com

mobile-imaging-004.p4.releng.scl1.mozilla.com
foopy60.p4.releng.scl1.mozilla.com
foopy61.p4.releng.scl1.mozilla.com
foopy62.p4.releng.scl1.mozilla.com
foopy63.p4.releng.scl1.mozilla.com
foopy64.p4.releng.scl1.mozilla.com
foopy65.p4.releng.scl1.mozilla.com
foopy66.p4.releng.scl1.mozilla.com

foopy56.p3.releng.scl1.mozilla.com appears to have a disk issue (bug 806662)

Comment 4

[Amy Rich [:arr] [:arich]]

The rest of the machines have been kickstarted:

mobile-imaging-006.p6.releng.scl1.mozilla.com
mobile-imaging-007.p7.releng.scl1.mozilla.com
mobile-imaging-008.p8.releng.scl1.mozilla.com
mobile-imaging-009.p9.releng.scl1.mozilla.com
mobile-imaging-010.p10.releng.scl1.mozilla.com

foopy74.p6.releng.scl1.mozilla.com
foopy75.p6.releng.scl1.mozilla.com
foopy76.p6.releng.scl1.mozilla.com
foopy77.p6.releng.scl1.mozilla.com
foopy78.p6.releng.scl1.mozilla.com
foopy79.p6.releng.scl1.mozilla.com
foopy80.p6.releng.scl1.mozilla.com
foopy81.p7.releng.scl1.mozilla.com
foopy82.p7.releng.scl1.mozilla.com
foopy83.p7.releng.scl1.mozilla.com
foopy84.p7.releng.scl1.mozilla.com
foopy85.p7.releng.scl1.mozilla.com
foopy86.p7.releng.scl1.mozilla.com
foopy87.p7.releng.scl1.mozilla.com
foopy88.p8.releng.scl1.mozilla.com
foopy89.p8.releng.scl1.mozilla.com
foopy90.p8.releng.scl1.mozilla.com
foopy91.p8.releng.scl1.mozilla.com
foopy92.p8.releng.scl1.mozilla.com
foopy93.p8.releng.scl1.mozilla.com
foopy94.p8.releng.scl1.mozilla.com
foopy95.p9.releng.scl1.mozilla.com
foopy96.p9.releng.scl1.mozilla.com
foopy97.p9.releng.scl1.mozilla.com
foopy98.p9.releng.scl1.mozilla.com
foopy99.p9.releng.scl1.mozilla.com
foopy100.p9.releng.scl1.mozilla.com
foopy101.p9.releng.scl1.mozilla.com
foopy102.p10.releng.scl1.mozilla.com
foopy103.p10.releng.scl1.mozilla.com
foopy104.p10.releng.scl1.mozilla.com
foopy105.p10.releng.scl1.mozilla.com
foopy106.p10.releng.scl1.mozilla.com
foopy107.p10.releng.scl1.mozilla.com
foopy108.p10.releng.scl1.mozilla.com