Closed
Bug 913206
Opened 11 years ago
Closed 11 years ago
revert changes for separate panda android pools after panda mobile mozharness changes land
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 829211
People
(Reporter: kmoir, Assigned: kmoir)
References
Details
Attachments
(1 file, 2 obsolete files)
12.70 KB,
patch
|
Details | Diff | Splinter Review |
In bug 894512, different pools were created for non-mozpool and mozpool managed pandas because of the way reboots are managed. This change can be reverted once the changes in bug 829211 are finished and in production since then all pandas will be managed by mozpool. I think it would be good to implement this change after the mozharness scripts have landed because there are some changed needed in lifeguard to change some of the devices from locked to free state etc.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → kmoir
Assignee | ||
Comment 1•11 years ago
|
||
Might be a good idea to do the part that removes the puppet definitions and bbcustom bits in a second reconfig after the first one is done in case there are tests still running
Assignee | ||
Comment 2•11 years ago
|
||
Attachment #804690 -
Attachment is obsolete: true
Assignee | ||
Comment 3•11 years ago
|
||
Attachment #807018 -
Attachment is obsolete: true
Assignee | ||
Comment 4•11 years ago
|
||
I decided to attach the patches in bug 829211 because of the changes required to enable the branches etc.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•4 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
•