Closed Bug 750793 (tegra-017) Opened 13 years ago Closed 11 years ago

[staging] tegra-017 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

x86
macOS
task
Not set
normal

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.
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]
nvram has been re-flashed and sdcard reinitialized
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Sending this slave to recovery -->Automated reopening of bug
Status: RESOLVED → REOPENED
Depends on: 896572
Resolution: FIXED → ---
reflashed and reimaged.
Product: mozilla.org → Release Engineering
Depends on: 913321
Status: REOPENED → RESOLVED
Closed: 13 years ago11 years ago
Resolution: --- → FIXED
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 → ---
No longer blocks: 925447
Depends on: 925447
Needed some help rebooting, but is reconnected to the staging master now.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
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.