Confirmed users
1,989
edits
ReleaseEngineering/Archive/Android Tegras: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Archive/Android Tegras (view source)
Revision as of 20:52, 13 May 2014
, 13 May 2014→How to deal with failing pandas in mozpool
| Line 456: | Line 456: | ||
* Devices in the "failed_pxe_booting" state in mozpool. Not sure what to do in this state since requests to reboot or reimage are refused because the device isn't available on the network. Opening a bug with DC Ops to investigate this device is a good first step. | * Devices in the "failed_pxe_booting" state in mozpool. Not sure what to do in this state since requests to reboot or reimage are refused because the device isn't available on the network. Opening a bug with DC Ops to investigate this device is a good first step. | ||
== Releng updates needed when moving panda racks from one data centre to another == | |||
We are in the process of moving pandas from scl1 to scl3 in {{bug|1001705}}. Here are the changes that are needed to implement this from the releng side of things | |||
* update devices.json in tools repo so relays point to correct data centre. Example: https://bugzilla.mozilla.org/attachment.cgi?id=8419438&action=edit | |||
* Relops will reimage the foopies. The directories in /builds will need to be recreated. ssh to the newly imaged foopies as root, cd /builds; for (( c=first; c<=last ; c++ )); do mkdir panda-0$c; done; chown cltbld.cltbld panda-0* | |||
* In slaveallco: update the datacentre they belong to and enable the pandas | |||
= References = | = References = | ||