News

TUgitLab malfunction fixed

The cause was a malfunction of a node of the underlying Kubernetes cluster, caused by a problem with the hypervisor. The affected pods could not be restarted automatically by the scheduler of the cluster because locks got stuck in the persistent volumes of the NFS storage due to the unclean termination.

We apologize for the inconvenience!