Closed
Bug 1148116
Opened 10 years ago
Closed 10 years ago
take foopy65 and foopy103 out of production
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jlund, Unassigned)
References
Details
this consists of disabling the associated pandas attached to them (see devices.json) via slavealloc.
we can then shutdown the foopies.
to bring them back we need to re-create the panda dirs. this can be done with a manage_foopies call:
tools/buildfarm/maintenance/manage_foopies.py -f ../mobile/devices.json -H $foopy create_device_dirs
Reporter | ||
Updated•10 years ago
|
Blocks: panda-0035, panda-0036, panda-0037, panda-0038, panda-0039, panda-0040, panda-0041, panda-0042, panda-0043, panda-0044, panda-0046, panda-0047, panda-0408, panda-0409, panda-0410, panda-0411, panda-0412, panda-0413, panda-0414, panda-0415, panda-0416, panda-0417, panda-0418, panda-0419, panda-0420, panda-0902
Reporter | ||
Updated•10 years ago
|
Assignee: server-ops-dcops → nobody
Component: DCOps → Buildduty
Product: Infrastructure & Operations → Release Engineering
QA Contact: bugspam.Callek
Reporter | ||
Comment 1•10 years ago
|
||
waiting for half a dozen pandas to finish up
Reporter | ||
Comment 2•10 years ago
|
||
all pandas have been disabled. foopies can be taken offline now.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•10 years ago
|
||
1146130 is complete. I'm reversing this patch and enabling the pandas again
Reporter | ||
Comment 4•10 years ago
|
||
that's done now
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•