Keep /var/lib/puppet/state/last_run_summary.yaml on captured AMIs

RESOLVED WONTFIX

Status

Product:
Infrastructure & Operations
Component:
RelOps: Puppet
Status:
RESOLVED WONTFIX
Reported:
4 years ago
Modified:
2 years ago

People

(Reporter: dustin, Unassigned)

Tracking

Details
(Reporter)

Description

•
4 years ago 
The sysmediumconfig1 security guideline is tested for by checking that last_run_summary.yaml is less than 15 days old.  It's failing for all spot instances, though.

The guideline is basically verifying that puppet has run "reasonably recently" on the host, which is a perfectly valid expectation for spot AMIs, too -- they should have been generated "reasonably recently".

It looks like this file goes missing when puppet is uninstalled.  Just touching it when baking the AMI should be sufficient.
Assignee: dustin → nobody
QA Contact: pmoore → mshal

Updated

•
2 years ago
Assignee: nobody → relops
Component: Other → RelOps: Puppet
Product: Release Engineering → Infrastructure & Operations
QA Contact: mshal → mcornmesser

Comment 1

•
2 years ago 
This will be replaced by whatever taskcluster is doing.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.