New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 900003 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Puppet change breaking puppet on all windows machines didn't page anyone from Labs team

Project Member Reported by iannu...@google.com, Oct 29

Issue description

CL in question: https://chrome-internal.googlesource.com/infra/puppet/+/41a3a0a6bfad8658f477fd89af343d2c45c35d63

This caused a 3 hour outage for the chromium CQ, and resulted in postmortem 97.

It would be good to understand why the folks on that CL didn't immediately recognize the problem once it was deployed and fix/revert it, and why no one on Labs was notified that windows machines were failing puppet runs due to this change.
 
Components: Infra>Labs
guessing at a component here
Cc: actodd@chromium.org friedman@chromium.org

Sign in to add a comment