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

Incidents/2022-08-16 Beta Cluster 502

From Wikitech-static
< Incidents
Revision as of 00:37, 17 August 2022 by imported>Samtar (→‎Scorecard)
(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-08-16 Beta Cluster 502 Start 2022-08-16 17:57:00
Task T315350 End 2022-08-17 00:57:00
People paged 0 Responder count 4
Coordinators Affected metrics/SLOs No relevant SLOs exist
Impact All sites within the Beta Cluster were unavailable, which affected CI workflows

After an inadvertent restart of some WMCS cloudvirts and their associated VMs, all sites within the Beta Cluster (e.g. failed to load, with Error: 502, Next Hop Connection Failed — this persisted post-restart of the relevant VMs.

Drafting: possibly an apache config/puppet failure (, restarting trafficserver seems to have fixed it (

Summary of what happened, in one or two paragraphs. Avoid assuming deep knowledge of the systems here, and try to differentiate between proximate causes and root causes.


Link to relevant source code, graphs, or logs


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.

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


Incident Engagement ScoreCard
Question Answer


People Were the people responding to this incident sufficiently different than the previous five incidents? no
Were the people who responded prepared enough to respond effectively yes
Were fewer than five people paged? yes
Were pages routed to the correct sub-team(s)? no
Were pages routed to online (business hours) engineers? Answer “no” if engineers were paged after business hours. no
Process Was the incident status section actively updated during the incident? yes
Was the public status page updated? no
Is there a phabricator task for the incident? yes
Are the documented action items assigned? no
Is this incident sufficiently different from earlier incidents so as not to be a repeat occurrence? yes
Tooling To the best of your knowledge was the open task queue free of any tasks that would have prevented this incident? Answer “no” if there are

open tasks that would prevent this incident or make mitigation easier if implemented.

Were the people responding able to communicate effectively during the incident with the existing tooling?
Did existing monitoring notify the initial responders? no
Were the engineering tools that were to be used during the incident, available and in service?
Were the steps taken to mitigate guided by an existing runbook? no
Total score (count of all “yes” answers above)