Closed Bug 1436097 Opened 7 years ago Closed 7 years ago

Golden AMI - Critical Alert

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bcrisan, Assigned: dhouse)

References

Details

From my understandings dhouse made some changes yesterday Irc aws manager allerts: aws-manager2.srv.releng.scl3.mozilla.com:procs age - golden AMI is CRITICAL: ELAPSED CRITICAL: 10 crit, 0 warn out of 10 processes with args 'ec2-golden' (http://m.mozilla.org/procs+age+-+golden+AMI)
Flags: needinfo?(dhouse)
Assignee: nobody → dhouse
I pushed a change to add cltbld to the kvm group on ubuntu machines. the kvm group does not exist on the 32bit ubuntu machines in aws, and the group 'kvm' did not exist when the cltbld user was created on the 64bit ubuntu machines (created in the package qemu-kvm). The puppet failures for the golden builds have stopped. I am waiting to see if the nagios check on aws-manager recovers because of puppet now completing correctly.
Blocks: 1435058
Flags: needinfo?(dhouse)
It looks like the alerts have cleared from nagios.
Status: NEW → RESOLVED
Closed: 7 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.