Closed Bug 838453 (tegra-356) Opened 12 years ago Closed 11 years ago

tegra-356 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

ARM
Android

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Unassigned)

References

()

Details

(Whiteboard: [buildduty][buildslaves][capacity])

No jobs taken on this device for >= 7 weeks
(mass change: filter on tegraCallek02reboot2013) I just rebooted this device, hoping that many of the ones I'm doing tonight come back automatically. I'll check back in tomorrow to see if it did, if it does not I'll triage next step manually on a per-device basis. --- Command I used (with a manual patch to the fabric script to allow this command) (fabric)[jwood@dev-master01 fabric]$ python manage_foopies.py -j15 -f devices.json `for i in 021 032 036 039 046 048 061 064 066 067 071 074 079 081 082 083 084 088 093 104 106 108 115 116 118 129 152 154 164 168 169 174 179 182 184 187 189 200 207 217 223 228 234 248 255 264 270 277 285 290 294 295 297 298 300 302 304 305 306 307 308 309 310 311 312 314 315 316 319 320 321 322 323 324 325 326 328 329 330 331 332 333 335 336 337 338 339 340 341 342 343 345 346 347 348 349 350 354 355 356 358 359 360 361 362 363 364 365 367 368 369; do echo '-D' tegra-$i; done` reboot_tegra The command does the reboot, one-at-a-time from the foopy the device is connected from. with one ssh connection per foopy
Depends on: 838687
Back from recovery
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Sending this slave to recovery -->Automated reopening of bug
Status: RESOLVED → REOPENED
Depends on: 889567
Resolution: FIXED → ---
Depends on: 892096
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 896572
Resolution: FIXED → ---
reflashed and reimaged.
Product: mozilla.org → Release Engineering
16:46 < nagios-releng> Wed 13:46:36 PDT [4533] tegra-356.build.mtv1.mozilla.com:tegra agent check is CRITICAL: Connection refused (http://m.allizom.org/tegra+agent+check) pdu reboot didn't help
Depends on: 912682
recovery didn't help, dunno what to do
Automation Error: Unable to connect to device after 5 attempts
Depends on: 928492
Remote Device Error: unable to write to sdcard
Depends on: 934493
agent check failing, pdu reboot didn't help
Depends on: 937173
flashed and reimaged
15:56 nagios-releng: Thu 12:56:31 PST [4968] tegra-356.build.mtv1.mozilla.com is DOWN :PING CRITICAL - Packet loss = 100%
Depends on: 944498
I've tried power-cycling it first.
flashed and reimaged
Depends on: 949447
sdcard replaced and reimaged/flashed.
handled in last recovery on Dec 16.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 959689
Resolution: FIXED → ---
This tegra died during the move.
2014-01-15 11:35:15 tegra-356 p OFFLINE active OFFLINE :: PING tegra-356.tegra.releng.scl3.mozilla.com (10.26.86.10) 56(84) bytes of data. From foopy30.tegra.releng.scl3.mozilla.com (10.26.84.6) icmp_seq=2 Destination Host Unreachable;error.flg [Automation Error: Unable to ping device after 5 attempts] pdu reboot didn't help
Depends on: 960642
this tegra was decommissioned in another bug; died during move.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
decomm'd in slavealloc
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.