March 26th by email to firstname.lastname@example.org from catlee: since we don't yet have a known cause or fix for the AMI issues we hit today, I've disabled AMI generation on aws-manager2 via commenting out the following cron jobs in /etc/cron.d/: puppetcheck aws_manager-aws_publish_amis.py.cron aws_manager-bld-linux64-ec2-golden.cron aws_manager-try-linux64-ec2-golden.cron aws_manager-tst-emulator64-ec2-golden.cron aws_manager-tst-linux32-ec2-golden.cron aws_manager-tst-linux64-ec2-golden.cron To restore, we should just need to re-enable the puppetcheck cron, and puppet will take care of the rest.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1149580
Component: Tools → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.