canmove, Confirmed users
112
edits
Connect and Troubleshoot workers in CI: Difference between revisions
Connect and Troubleshoot workers in CI (view source)
Revision as of 00:44, 16 April 2019
, 16 April 2019changed a link
(add a new method to fix the chassis issue) |
m (changed a link) |
||
| Line 6: | Line 6: | ||
If we cannot ssh into OSX nodes, we can try to restart them from Taskcluster. But if they are not visible in the Taskcluster worker explorer, then you can create them using this version of [https://github.com/davehouse/relops-infra/blob/quarantine_nonexisting/quarantine_tc.py quarantine script] that will add/define a worker if it is missing. | If we cannot ssh into OSX nodes, we can try to restart them from Taskcluster. But if they are not visible in the Taskcluster worker explorer, then you can create them using this version of [https://github.com/davehouse/relops-infra/blob/quarantine_nonexisting/quarantine_tc.py quarantine script] that will add/define a worker if it is missing. | ||
* Step 1: [[ | * Step 1: [[CIDuty:TaskClusterCli|Connect to Taskcluster CLI]] | ||
* Step 2: Use this command: e.g. <code>python quarantine_tc.py --enable -p releng-hardware -w gecko-t-osx-1010 -g mdc2 t-yosemite-r7-449</code> | * Step 2: Use this command: e.g. <code>python quarantine_tc.py --enable -p releng-hardware -w gecko-t-osx-1010 -g mdc2 t-yosemite-r7-449</code> | ||