Add bilbo reboot caused by scw
This commit is contained in:
parent
69a8fe7918
commit
f4fc81f5a2
1 changed files with 32 additions and 0 deletions
32
content/issues/bilbo-scw-incident.md
Normal file
32
content/issues/bilbo-scw-incident.md
Normal file
|
@ -0,0 +1,32 @@
|
|||
---
|
||||
title: Bilbo Reboot
|
||||
date: 2020-09-20 14:00:00
|
||||
resolved: false
|
||||
# resolvedWhen: 2020-09-20 17:00:00
|
||||
# Possible severity levels: down, disrupted, notice
|
||||
severity: notice
|
||||
affected:
|
||||
- bilbo
|
||||
- pbin.papey.fr
|
||||
- bobuncer.papey.fr
|
||||
- stdio.space
|
||||
- kancer.club
|
||||
- blog.papey.fr
|
||||
- papey.fr
|
||||
- brain.papey.fr
|
||||
section: issue
|
||||
---
|
||||
|
||||
## Context
|
||||
|
||||
Trying to get rid of this [bad state on SCW
|
||||
hypervisor](https://status.scaleway.com/incident/421) causing unability to
|
||||
snapshot the instance
|
||||
|
||||
In a Twitter thread, the SCW team stays that a [reboot should be
|
||||
enough](https://twitter.com/Scaleway_Help/status/1303300620917633024) so
|
||||
let's try.
|
||||
|
||||
## Status
|
||||
|
||||
This server will be rebooted on 2020-09-20 at 14:00PM.
|
Loading…
Add table
Reference in a new issue