Closed Bug 1047979 (foopy32) Opened 11 years ago Closed 11 years ago

foopy32 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

x86
All
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: Callek)

References

Details

Attachments

(1 file)

Fell over, starting at: ***** Nagios ***** Notification Type: PROBLEM Host: foopy32.tegra.releng.scl3.mozilla.com State: DOWN Address: 10.26.84.8 Info: PING CRITICAL - Packet loss = 100% Date/Time: 08-02-2014 11:18:17 From the FQDN and tools/buildfarm/mobile/devices.json this is tegra only, so no problem for it to be dead. Nightly won't let me reach foopy32-mgmt.build.m.o (invalid CA error), and I didn't try any harder to reboot it.
Should we decomm the foopy and all its tegras? (like bug 1043938)
Blocks: 1048305
Blocks: tegra-198
Blocks: tegra-202
Blocks: tegra-352
Blocks: tegra-353
Blocks: tegra-354
Blocks: tegra-355
Blocks: tegra-357
Blocks: tegra-363
Blocks: tegra-369
Attached patch [tools] v1Splinter Review
Assignee: nobody → bugspam.Callek
Status: NEW → ASSIGNED
Attachment #8467355 - Flags: review?(pmoore)
Comment on attachment 8467355 [details] [diff] [review] [tools] v1 Review of attachment 8467355 [details] [diff] [review]: ----------------------------------------------------------------- Flawless!
Attachment #8467355 - Flags: review?(pmoore) → review+
Status: ASSIGNED → RESOLVED
Closed: 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.

Attachment

General

Created:
Updated:
Size: