You are browsing a read-only backup copy of Wikitech. The live site can be found at

Incidents/2022-05-01 etcd

From Wikitech-static
< Incidents
Revision as of 22:10, 2 May 2022 by imported>Cwhite (→‎Summary: add logstash link)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

document status: draft


Incident metadata (see Incident Scorecard)
Incident ID 2022-05-01 etcd Start 04:48
Task T307382 End 06:38
People paged 15 Responder count 2
Coordinators dzahn, cwhite Affected metrics/SLOs
Impact conftool-data could not be synced between data centers, puppet-merge showed sync errors, wikitech (labweb) hosts showed failed systemd timers

The TLS certificate for etcd.eqiad.wmnet expired. nginx servers on conf* machines use this certificate. conftool-data could not be synced between conf hosts anymore. puppet-merge showed sync errors. labweb (wikitech) hosts alerted because of failed timers/jobs. We got paged due to monitoring of "Etcd replication lag". We had to renew the certificate but it wasn't a simple renew because additionally some certificates had already converted to a new way or creating and managing them while others had not. Both main data centers were in different states. Only eqiad was affected. After figuring this out eventually we created a new certificate for etcd.eqiad using cergen, copied the private key and certs in place and reconfigured servers in eqiad to use it. After this all alerts recovered.



Create a list of action items that will help prevent this from happening again as much as possible. Link to or create a Phabricator task for every step.

  • T307382 (Modernize etcd tlsproxy certificate management)
  • T307383 (Certificate expiration monitoring)

TODO: Add the #Sustainability (Incident Followup) and the #SRE-OnFIRE (Pending Review & Scorecard) Phabricator tag to these tasks.


Incident Engagement™ ScoreCard
Question Score Notes
People Were the people responding to this incident sufficiently different than the previous five incidents? (score 1 for yes, 0 for no)
Were the people who responded prepared enough to respond effectively (score 1 for yes, 0 for no)
Were more than 5 people paged? (score 0 for yes, 1 for no)
Were pages routed to the correct sub-team(s)? (score 1 for yes, 0 for no)
Were pages routed to online (business hours) engineers? (score 1 for yes,  0 if people were paged after business hours)
Process Was the incident status section actively updated during the incident? (score 1 for yes, 0 for no)
Was the public status page updated? (score 1 for yes, 0 for no)
Is there a phabricator task for the incident? (score 1 for yes, 0 for no)
Are the documented action items assigned?  (score 1 for yes, 0 for no)
Is this a repeat of an earlier incident (score 0 for yes, 1 for no)
Tooling Was there, before the incident occurred, open tasks that would prevent this incident / make mitigation easier if implemented? (score 0 for yes, 1 for no)
Were the people responding able to communicate effectively during the incident with the existing tooling? (score 1 for yes, 0 or no)
Did existing monitoring notify the initial responders? (score 1 for yes, 0 for no)
Were all engineering tools required available and in service? (score 1 for yes, 0 for no)
Was there a runbook for all known issues present? (score 1 for yes, 0 for no)
Total score