Closed
Bug 822061
(tegra-363)
Opened 12 years ago
Closed 10 years ago
tegra-363 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Callek, Unassigned)
References
()
Details
(Whiteboard: [buildduty][buildslaves][capacity])
Needs a reimage, unable to connect to SUT port
Comment 1•12 years ago
|
||
Tegra reimaged. No SD swap.
Comment 2•12 years ago
|
||
pdu reboot
start_cp
Reporter | ||
Comment 5•12 years ago
|
||
(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
Reporter | ||
Comment 6•12 years ago
|
||
Back from recovery
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 7•12 years ago
|
||
72 days, 1:17:00 since last job
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 8•12 years ago
|
||
recovery didn't help, dunno what to do
Reporter | ||
Comment 9•11 years ago
|
||
Sending this slave to recovery
-->Automated message.
Depends on: 889567
Reporter | ||
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Comment 10•11 years ago
|
||
Hasn't taken a job for 7 days.
Status: RESOLVED → REOPENED
QA Contact: armenzg → bugspam.Callek
Resolution: FIXED → ---
Comment 11•10 years ago
|
||
Disabled in slavealloc to stop the stream of pointless reboots.
Comment 12•10 years ago
|
||
SD card replaced, tegra flashed and reimaged.
vle@vle-10516 ~ $ telnet tegra-363.tegra.releng.scl3.mozilla.com 20701
Trying 10.26.86.14...
Connected to tegra-363.tegra.releng.scl3.mozilla.com.
Escape character is '^]'.
$>^]
telnet> q
Comment 13•10 years ago
|
||
Reenabled.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
Comment 14•10 years ago
|
||
Still hasn't taken a job, I think it's more busted than just recovery.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 15•10 years ago
|
||
replaced SD card, flashed and reimaged tegra.
vle@vle-10516 ~ $ telnet tegra-363.tegra.releng.scl3.mozilla.com 20701
Trying 10.26.86.14...
Connected to tegra-363.tegra.releng.scl3.mozilla.com.
Escape character is '^]'.
$>^]
telnet> q
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•10 years ago
|
Comment 16•10 years ago
|
||
All tegras are being decommissioned.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•