You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org
Incidents/2022-05-02 deployment: Difference between revisions
Jump to navigation
Jump to search
imported>Quiddity m (Quiddity moved page Incidents/2022-05-2 deployment to Incidents/2022-05-02 deployment: fix naming for list order) |
imported>Krinkle |
||
| Line 3: | Line 3: | ||
==Summary== | ==Summary== | ||
{{Incident scorecard | {{Incident scorecard | ||
| task =T307349 | | task = T307349 | ||
| paged-num =0 | | paged-num = 0 | ||
| responders-num =4 | | responders-num = 4 | ||
| coordinators =Jaime Crespo | | coordinators = Jaime Crespo | ||
| start =2022-05-02 11:13 | | start = 2022-05-02 11:13 | ||
| end =2022-05-02 15:21 | | end = 2022-05-02 15:21 | ||
|metrics=No relevant SLOs exist|impact= | | metrics = No relevant SLOs exist | ||
| impact = For 4 hours, MediaWiki and other services could not be updated or deployed due to data loss on the active deployment server. | |||
}} | |||
<!-- Reminder: No private information on this page! --> | <!-- Reminder: No private information on this page! --> | ||
Parts of <code>/srv/deployment</code> were lost on active [[deployment server]] (deploy1002) due to the wrong command, <code>rm -rf</code>, being executed. This halted deployments for some time, until we were able to restore the directory from a backup and we checked it for correctness. | |||
'''Documentation''': | '''Documentation''': | ||
* | *[[phab:T307349|T307349]] | ||
*[[Bacula|Bacula backups]] | |||
==Actionables== | ==Actionables== | ||
Latest revision as of 16:50, 15 June 2022
document status: draft
Summary
| Incident ID | 2022-05-02 deployment | Start | 2022-05-02 11:13 |
|---|---|---|---|
| Task | T307349 | End | 2022-05-02 15:21 |
| People paged | 0 | Responder count | 4 |
| Coordinators | Jaime Crespo | Affected metrics/SLOs | No relevant SLOs exist |
| Impact | For 4 hours, MediaWiki and other services could not be updated or deployed due to data loss on the active deployment server. | ||
Parts of /srv/deployment were lost on active deployment server (deploy1002) due to the wrong command, rm -rf, being executed. This halted deployments for some time, until we were able to restore the directory from a backup and we checked it for correctness.
Documentation:
Actionables
Scorecard
| Question | Answer
(yes/no) |
Notes | |
|---|---|---|---|
| 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. | / | ||
| 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 | ||
| 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 | ||
| Total score (count of all “yes” answers above) | |||