Status

Infrastructure & Operations
DCOps
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: Callek, Unassigned)

Tracking

Details

(Whiteboard: [Recovering])

(Reporter)

Description

5 years ago
+++ This bug was initially created as a clone of Bug #889567 +++

From Bug 889567 there are a handful of devices that are still not recovering...

Please swap in new sdcards on:
* 121
* 311
* 363

Reimage, with more checks than just ping (see below):
* 056
* 093
* 121
* 195
* 295
* 307
* 311
* 323
* 328
* 339
* 345
* 346
* 356
* 360
* 363
* 364
* 368

Please reimage all of these, and in addition to ping, check a |telnet $deviceIP 20701| if the connection succeeds and yields a prompt then you can simply exit said prompt with |quit|

(details):

tegra-056 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
tegra-093 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
tegra-121 -  not running -    enabled - 'Remote Device Error: unable to write to sdcard'
tegra-195 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
tegra-295 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
tegra-307 -  not running -    enabled - 'Automation Error: Unable to ping device after 5 attempts'
tegra-311 -  not running -    enabled - 'Remote Device Error: unable to write to sdcard'
tegra-323 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
tegra-328 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
tegra-339 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
tegra-345 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
tegra-346 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
tegra-356 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
tegra-360 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
tegra-363 -  not running -    enabled - 'Remote Device Error: unable to write to sdcard'
tegra-364 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
tegra-368 -  not running -    enabled - 'Automation Error: Unable to connect to device after 5 attempts'
(Reporter)

Updated

5 years ago
Blocks: 778896

Updated

5 years ago
colo-trip: --- → mtv1
Tegras has been reimaged

* 056
* 093
* 121
* 195
* 295
* 307
* 311
* 323
* 328
* 339
* 345
* 346
* 356
* 360
* 363
* 364
* 368

Tegras has been reimaged and SD card has been swapped.

* 121
* 311
* 363

Will update if its reachable, in addition to ping will also check|telnet $deviceIP 20701|

Comment 2

5 years ago
There seems to be an issues with tegra 307 and 364. Tegra 307 has been reimaged 3 times and sd card has been swapped but I am still unable to ping it. Tegra 364 has also been reimaged 3 times and the sd card has been swapped. I am able to ping it but I can't connect with telnet. The rest of the tegras were able to ping and connect with telnet.

tegra-056.build.mtv1.mozilla.com is alive
tegra-121.build.mtv1.mozilla.com is alive
tegra-051.build.mtv1.mozilla.com is alive
tegra-307.build.mtv1.mozilla.com is unreachable
tegra-328.build.mtv1.mozilla.com is alive
tegra-093.build.mtv1.mozilla.com is alive
tegra-323.build.mtv1.mozilla.com is alive
tegra-295.build.mtv1.mozilla.com is alive
tegra-311.build.mtv1.mozilla.com is alive
tegra-363.build.mtv1.mozilla.com is alive
tegra-360.build.mtv1.mozilla.com is alive
tegra-346.build.mtv1.mozilla.com is alive
tegra-339.build.mtv1.mozilla.com is alive
tegra-368.build.mtv1.mozilla.com is alive
tegra-345.build.mtv1.mozilla.com is alive
tegra-356.build.mtv1.mozilla.com is alive
tegra-364.build.mtv1.mozilla.com is alive
tegra-195.build.mtv1.mozilla.com is alive

Trying 10.250.49.43...
Connected to tegra-056.build.mtv1.mozilla.com.

Trying 10.250.51.151...
Connected to tegra-311.build.mtv1.mozilla.com.

Trying 10.250.50.31...
Connected to tegra-121.build.mtv1.mozilla.com.

Trying 10.250.49.38...
Connected to tegra-051.build.mtv1.mozilla.com.

Trying 10.250.51.168...
Connected to tegra-328.build.mtv1.mozilla.com.

Trying 10.250.49.81...
Connected to tegra-093.build.mtv1.mozilla.com.

Trying 10.250.51.163...
Connected to tegra-323.build.mtv1.mozilla.com.

Trying 10.250.51.135...
Connected to tegra-295.build.mtv1.mozilla.com.

Trying 10.250.51.203...
Connected to tegra-363.build.mtv1.mozilla.com.

Trying 10.250.51.200...
Connected to tegra-360.build.mtv1.mozilla.com.

Trying 10.250.51.186...
Connected to tegra-346.build.mtv1.mozilla.com.

Trying 10.250.51.179...
Connected to tegra-339.build.mtv1.mozilla.com.

Trying 10.250.51.208...
Connected to tegra-368.build.mtv1.mozilla.com.

Trying 10.250.51.185...
Connected to tegra-345.build.mtv1.mozilla.com.

Trying 10.250.51.196...
Connected to tegra-356.build.mtv1.mozilla.com.

Trying 10.250.50.105...
Connected to tegra-195.build.mtv1.mozilla.com.
(Reporter)

Comment 3

5 years ago
thanks, many of these are still *acting* down, I'm exploring a harder stance on just calling them dead-for-good though.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Reporter)

Updated

5 years ago
Alias: tegra-recovery
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.