Closed Bug 986059 Opened 10 years ago Closed 7 years ago

AWS sanity check improvements

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: armenzg, Unassigned)

Details

From bug 962190:

I have some more improvements to mention:
* We have dozens of "None" lines [1] (282 out of 376 lines)
* We have 90+ tst-linux64-spot-XXX instances that have been up for more than 12 hours (up to 356 hours)
** However, they have been doing jobs all this time
** only some of them had not done jobs recently (and they appeared on the "lazy instances" section - bug 984893)

[1] 196 None (i-19533b11, us-west-2): up for 7 hours (no info from buildapi)

Can we send the following sections to a separate audience?
* ==== Instances with unknown type ====
* ==== Instances with unknown state ====
* ==== Instances stopped for a while ====
* ==== Not attached volumes ====
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.