Partial Access Restoration - Data Retrieval on SCITAS Clusters#
We would like to inform you that the frontends of the Jed and Kuma clusters have now been reopened in order to allow users to retrieve their data.
At this stage, users with running jobs on a given cluster will not be able to connect to its corresponding frontend. This is because the compute nodes hosting these jobs have not yet been redeployed and therefore remain vulnerable.
As a temporary workaround, users running jobs on Kuma may retrieve their data via the Jed frontend, and vice versa, as long as the data are not located on scratch.
Please note that the host keys of the frontends have been changed. When connecting, you should expect new SSH fingerprints. The expected fingerprints are available on the following pages:
During our investigation, we identified 193 private SSH keys stored in user home directories that could grant access to the clusters. To mitigate any risk of identity impersonation, access using these keys has been disabled. As a consequence, affected users will need to log in using their Gaspar password and then deploy a new, clean public SSH key.
If you have an urgent need to access a specific cluster where you currently have running jobs, you may contact us by opening a support ticket to request the termination of your jobs.
We appreciate your understanding and cooperation as we continue to restore the service safely.