Closed Bug 751686 (tegra-019) Opened 12 years ago Closed 11 years ago

[staging] tegra-019 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: armenzg, Unassigned)

References

(
URL
)

Details

(Whiteboard: [buildduty][buildslave][capacity]) 

[55] tegra-019.build.mtv1:tegra agent check is CRITICAL: Connection refused
Only down since Wed Morning:
2012-05-02 08:10:07 tegra-019 s  INACTIVE   active   active :: SUTAgent not present;

PDU-Cycled, checking back shortly
Summary: tegra-019 problem tracking → [staging] tegra-019 problem tracking
Whiteboard: [buildduty][buildslave][capacity]
Tegra power cycled, still unable to connect via command port -- this is in IT's hands now
nvram has been re-flashed and sdcard reinitialized
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 822038
Resolution: FIXED → ---
Can't connect to SUT Port
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Depends on: 913321
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
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 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.