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

Incidents/2022-05-2 deployment: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
imported>Elukey
(Created page with "{{irdoc|status=draft}} ==Summary== {{Incident scorecard | task =T307349 | paged-num =0 | responders-num =4 | coordinators =Jaime Crespo | start =2022-05-02 11:13 | end =2022-05-02 15:21 |metrics=No relevant SLOs exist|impact=Part of the content of /srv/deployment on deploy1002, the active deployment server, got lost due to the wrong command (rm -rf) being executed. This caused a stop in deployments for the time that it took to restore the directory and sanity chec...")
 
imported>Quiddity
(Quiddity moved page Incidents/2022-05-2 deployment to Incidents/2022-05-02 deployment: fix naming for list order)
 
Line 1: Line 1:
{{irdoc|status=draft}}
#REDIRECT [[Incidents/2022-05-02 deployment]]
 
==Summary==
{{Incident scorecard
| task =T307349
| paged-num =0
| responders-num =4
| coordinators =Jaime Crespo
| start =2022-05-02 11:13
| end =2022-05-02 15:21
|metrics=No relevant SLOs exist|impact=Part of the content of /srv/deployment on deploy1002, the active deployment server, got lost due to the wrong command (rm -rf) being executed. This caused a stop in deployments for the time that it took to restore the directory and sanity check it.}}
<!-- Reminder: No private information on this page! -->
 
Part of the content of <code>/srv/deployment</code> on <code>deploy1002</code>, the active deployment server, got lost due to the wrong command (<code>rm -rf</code>) being executed. This caused a stop in deployments for the time that it took to restore the directory and sanity check it.
 
'''Documentation''':
*All info contained in the task
 
==Actionables==
 
* https://phabricator.wikimedia.org/T309162
 
==Scorecard==
 
{| class="wikitable"
|+[[Incident Scorecard|Incident Engagement™  ScoreCard]]
!
!Question
!Answer
(yes/no)
!Notes
|-
! rowspan="5" |People
|Were the people responding to this incident sufficiently different than the previous five incidents?
|yes
|
|-
|Were the people who responded prepared enough to respond effectively
|yes
|
|-
|Were fewer than five people paged?
|no
|
|-
|Were pages routed to the correct sub-team(s)?
|/
|
|-
|Were pages routed to online (business hours) engineers?  ''Answer “no” if engineers were paged after business hours.''
|/
|
|-
! rowspan="5" |Process
|Was the incident status section actively updated during the incident?
|no
|
|-
|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
|
|-
! rowspan="5" |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.''
|yes
|
|-
|Were the people responding able to communicate effectively during the incident with the existing tooling?
|yes
|
|-
|Did existing monitoring notify the initial responders?
|no
|
|-
|Were all engineering tools required available and in service?
|yes
|
|-
|Was there a runbook for all known issues present?
|yes
|
|-
! colspan="2" align="right" |Total score (c'''ount of all “yes” answers above)'''
|
|
|}

Latest revision as of 19:48, 26 May 2022