If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.
Bug 754246 (tegra-152)

tegra-152 problem tracking

RESOLVED WONTFIX

Status

Release Engineering
Buildduty
RESOLVED WONTFIX
5 years ago
3 years ago

People

(Reporter: bhearsum, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

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

(Reporter)

Description

5 years ago
08:39 < nagios-sjc1> [08:30:53] [32] tegra-152.build.mtv1:PING is CRITICAL: PING CRITICAL - Packet loss = 100%


Didn't respond to a PDU reboot.
(Reporter)

Updated

5 years ago
Depends on: 754391
NVRAM reflashed and SDcard re-initialized.

Updated

5 years ago
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
No jobs taken on this device for > a day (< a week)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(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

Updated

5 years ago
Depends on: 838687
had to cycle clientproxy to bring this back
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → FIXED

Updated

4 years ago
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
(Reporter)

Comment 5

4 years ago
agent check failing, pdu reboot didn't help
Status: RESOLVED → REOPENED
Depends on: 937173
Resolution: FIXED → ---

Comment 6

4 years ago
flashed and reimaged
(Reporter)

Comment 7

4 years ago
Back in production.
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago4 years ago
Resolution: --- → FIXED
(Reporter)

Updated

4 years ago
Status: RESOLVED → REOPENED
Depends on: 974917
Resolution: FIXED → ---

Comment 8

4 years ago
sd card replaced, tegra flashed and reimaged.

[vle@admin1a.private.scl3 ~]$ fping tegra-152.tegra.releng.scl3.mozilla.com
tegra-152.tegra.releng.scl3.mozilla.com is alive

Updated

4 years ago
Depends on: 971859
Taking jobs again
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED
Hasn't taken a job for 10 days.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
All tegras are being decommissioned.
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.