Closed
Bug 750793
(tegra-017)
Opened 13 years ago
Closed 11 years ago
[staging] tegra-017 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Unassigned)
References
()
Details
(Whiteboard: [buildduty][buildslave][capacity])
[90] tegra-017.build.mtv1:tegra agent check is CRITICAL: Connection refused
It is a staging slave though.
Comment 1•13 years ago
|
||
Has been down since
2012-03-24 12:20:07 tegra-017 s INACTIVE active active :: SUTAgent not present;REBOOTING
foopy07 even shows buildbot as still active for this tegra too (so likely is burning some staging jobs, if its not hung). This tegra likely just needs a reflash so SUTAgent comes out ok.
Summary: tegra-017 problem tracking → [staging] tegra-017 problem tracking
Whiteboard: [buildduty][buildslave][capacity]
Comment 2•13 years ago
|
||
nvram has been re-flashed and sdcard reinitialized
Reporter | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 3•12 years ago
|
||
Sending this slave to recovery
-->Automated reopening of bug
Comment 4•12 years ago
|
||
reflashed and reimaged.
Updated•12 years ago
|
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 13 years ago → 11 years ago
Resolution: --- → FIXED
Comment 5•11 years ago
|
||
Watcher version needs upgrading - upgrade unsuccessful via script, requesting this tegra to be reimaged with the new image that has the latest Watcher (1.16).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•11 years ago
|
Comment 6•11 years ago
|
||
Needed some help rebooting, but is reconnected to the staging master now.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
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
•