Closed Bug 646645 Opened 13 years ago Closed 13 years ago

reimage tegras

Categories

(Infrastructure & Operations :: RelOps: General, task)

ARM
Android
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bear, Assigned: zandr)

Details

please pull and reimage Tegra 077 - it is
... pingable but not reachable via port 20701 :)
also:

tegra-017
tegra-069
tegra-080

This isn't urgent yet, since we have a fairly large usable pool, but if Spencer is looking for things to do we won't say no :)
Summary: reimage Tegra 077 → reimage tegras
Assignee: server-ops-releng → zandr
tegra-058 (on my desk) -- network issues.
need to reimage the following tegras:

tegra-031
tegra-033
tegra-034
tegra-036
tegra-037
tegra-038
tegra-041
tegra-043
tegra-045
tegra-048
tegra-049
tegra-050
tegra-051
tegra-052
tegra-054
tegra-059
tegra-061
tegra-062
tegra-063
tegra-064
tegra-069
tegra-073
tegra-082
tegra-083
tegra-087

they have either started right out in an error condition or worked up to one
Bear: can we figure out why?
blunt answer is "yes, but" ...

I didn't set up any type of metric or tracking and that is what I want to do monday: work up some sort of simple tracking so we can follow a tegra thru a week and see if some always have the same issues
ok, cancelling this request. after talking with aki I realize i'm using the "IT hammer" to solve issues that may be on our side and also I will be losing log info that could point to what the underlying issue is.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Agreed, that's 25 data points that we're going to need if we are going to move this towards any kind of operational stability
I don't think there's any "if" involved!
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.