Closed Bug 786366 (tegra-307) Opened 8 years ago Closed 7 years ago

decommission tegra-307

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Unassigned)

References

()

Details

(Whiteboard: [buildduty])

Didn't come back from a PDU reboot.
Whiteboard: [buildduty]
Back in production.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Didn't come back from a PDU reboot.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 792316
IT handled this, back to taking jobs
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
nagios has been yapping about it not responding to pings for so long that even I'm getting tired of the noise.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Apparently sometime during the intervening week it managed to respond once, since it was back to yapping again.
(In reply to Phil Ringnalda (:philor) from comment #5)
> Apparently sometime during the intervening week it managed to respond once,
> since it was back to yapping again.

During the week it physically moved and had itself restarted due to a power event in mtv1.
tried a pdu reboot, don't know what else to do.
Assignee: nobody → bugspam.Callek
Off to recovery
Assignee: bugspam.Callek → nobody
Depends on: 817995
Depends on: 822038
pdu reboot
start_cp.sh
Didn't come back, off to recovery (again):
10:16 < nagios-releng> Thu 07:16:39 PST [494] tegra-307.build.mtv1.mozilla.com is DOWN :PING CRITICAL - Packet loss = 100%
Depends on: 825335
the switch was set to BATT instead of NORM so the board wasn't powered on. reimaged SD card anyways.
This fell over again; not a promising sign.
Depends on: 830739
did a pdu reboot again, waiting that this thing comes up again
(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
now taking jobs
Status: REOPENED → RESOLVED
Closed: 8 years ago7 years ago
Resolution: --- → FIXED
9 days, 16:30:17 since last job
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 858134
neither pdu reboot nor recovery helped, dunno what to do
back in production
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
Depends on: 877722
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Came up, but with a LOT of problems through the day per https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slave.html?class=test&type=tegra&name=tegra-307

Its currently unpingable.

tegra-307 -  not running -    enabled - 'Automation Error: Unable to ping device after 5 attempts'
Sending this slave to recovery
-->Automated message.
Depends on: 889567
Depends on: 892096
Depends on: 896572
reflashed and reimaged.
Product: mozilla.org → Release Engineering
ping and agent checks failing, pdu reboot didn't help
Depends on: 912682
Tegra-307 keeps overheating, also a strong burning smell(tried different power supplies).


I'd rather decom this tegra do avoid something bad
(In reply to Salvador Espinoza [:sal] from comment #23)
> Tegra-307 keeps overheating, also a strong burning smell(tried different
> power supplies).
> 
> 
> I'd rather decom this tegra do avoid something bad

Sounds good, thanks for looking at it!
Summary: tegra-307 problem tracking → decommission tegra-307
Updated buildbot-configs and devices.json to reflect decomm.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
I also removed tegra-307 from foopy28
(on foopy28: rm -rf /builds/tegra-307)

Currently we do not have an automatic mechanism to keep the foopy device directories in sync with the devices.json file.
QA Contact: other → armenzg
Blocks: 959225
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.