Closed Bug 897002 Opened 10 years ago Closed 9 years ago

Report impaired AWS non slave machines

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rail, Assigned: massimo)

Details

In bug 896948 we "lost" one of the AWS buildbot masters. 

We can:
 * Report impaired non-slave instances (we shut down impaired slaves)
 * Reboot impaired instances. This won't change the underlying hardware.
 * Shut down the instance and start it when it's stopped. Stop may take some time, it may even require a forced stop or the EC2 bot which shuts down the instances stuck in the stop phase. Or we can split this into 2 separate watcher: one to stop impaired instances, and one to start stopped and tagged as "ready" instances.
Product: mozilla.org → Release Engineering
Assignee: rail → mgervasini
Hey rail,

the patch landed for bug 962190 adds impaired instances to the aws sanity check e-mail.
Fixed then?
Status: NEW → RESOLVED
Closed: 9 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.