Changes for page Announcements

Last modified by hbpadmin on 2025/01/09 12:12
From version 102.1
edited by mmorgan
on 2021/11/25 10:47
Change comment: There is no comment for this version
To version 107.1
edited by mmorgan
on 2021/12/28 17:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,24 @@
1 -== **Issue on the OpenShift server at CSCS (2021-11-24)** ==
1 +=== **Issue on the OpenShift server at CSCS (2021-12-28)** ===
2 2  
3 +The EBRAINS OpenShift server running at CSCS was detected as having come down. This issue affects all the services running on that OpenShift server including:
4 +
5 +* Collaboratory Lab,
6 +* image service,
7 +* atlas viewers,
8 +* simulation services (NEST desktop, TVB, Brain Simulation Platform)
9 +
10 +We are working with the CSCS team to reactivate the service ASAP.
11 +
12 +The service was reestablished at around 14:15 CET. The infrastructure team will continue looking into the potential causes of the problem with RedHat. The suspected cause lies in network access to the storage.
13 +
14 +=== **Issue on the Forum service (2021-12-27)** ===
15 +
16 +The Forum service went down over the weekend along with one of the redundant OpenShift servers. The issue was due to a problem at the infrastructure level.
17 +
18 +The Forum was unavailable for a few hours on Monday. There was not perceptible effect on the services running on OpenShift.
19 +
20 +=== **Issue on the OpenShift server at CSCS (2021-11-24)** ===
21 +
3 3  The EBRAINS OpenShift server running at CSCS was detected as having come down at 16:00 CEST. This issue affects all the services running on that OpenShift server including:
4 4  
5 5  * Collaboratory Lab,
... ... @@ -9,8 +9,10 @@
9 9  
10 10  We are working with the CSCS team and RedHat (provider of the OpenStack solution on which OpenShift runs) to reactivate the service ASAP.
11 11  
12 -The issue affected the central VM node of the OpenShift service. Restarting the VM required that we resolve multiple issues including restarting at the same IP address and unlocking the storage volumes of that VM. The central node has now been restarted. The same issue has occurred on three other instances of OpenShift VMs. We have the procedure for restarting those and are working on implementing it. The root cause seems to be at the infrastructure level and RedHat is involved in analyzing that.
31 +The issue affected the central VM node of the OpenShift service. Restarting the VM required that we resolve multiple issues including restarting at the same IP address and unlocking the storage volumes of that VM. (% style="color:#16a085" %)The central node has now been restarted. The same issue has occurred on three other instances of OpenShift VMs. They have been restarted too. OpenShift is up and running again. The DNS redirection(s) to the maintenance page is being removed. The services should be operational again.
13 13  
33 +(% style="color:#16a085" %)The root cause seems to be at the infrastructure level and RedHat is involved in analyzing that.
34 +
14 14  We will keep updating this page with more information as it comes in.
15 15  
16 16  === **Maintenance of multiple services (2021-11-11 to 2021-11-19)** ===