Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
habrok:additional_information:changelog [2026/01/06 12:59] – fokkehabrok:additional_information:changelog [2026/06/25 08:35] (current) – [2026-06-24] pedro
Line 2: Line 2:
  
 This page records major changes to Hábrók, which are mostly carried out during scheduled maintenance periods. This changelog is kept since August 13th 2025, although changes have been made during past scheduled maintenance periods and on-demand as necessary. This page records major changes to Hábrók, which are mostly carried out during scheduled maintenance periods. This changelog is kept since August 13th 2025, although changes have been made during past scheduled maintenance periods and on-demand as necessary.
 +
 +===== 2026-06-24 =====
 +
 +  * A new GPU node containing a single RTX PRO 6000 GPU and a AMD EPYC 9555P Zen5 GPU is now available. Users belonging to the Orion project have priority access. General users are limited to the ''gpushort'' partition in this node, see more details about [[..:advanced_job_management:special_partitions]].
 +
 +===== 2026-05-26 =====
 +
 +  * The GPU drivers have been updated to fix the issues described at https://nvidia.custhelp.com/app/answers/detail/a_id/5821 This means that all GPUs except the V100 GPUs are at driver version 595.71.05.  The V100 nodes have driver 580.159.04, as the later releases like versions 595 are no longer supported on those cards.
 +  * The driver updates mean that CUDA 13 is now supported on all GPUs except the V100 GPUs. Although the 580.159.04 driver states support for CUDA 13.0, it is not supported on the V100 GPUs. This means that on the V100 you will need to limit yourself to CUDA 12 based software.
 +
 +===== 2026-04-29 =====
 +
 +  * On the night of 2026-04-29 a security vulnerability -- [[https://access.redhat.com/security/cve/cve-2026-31431|CVE-2026-31431]] -- was published that affected most Linux systems in operation. This vulnerability allowed obtaining root privileges on systems by running a script that exploited a flaw in Linux's kernel. To prevent this vulnerability from being exploited, we brought down all Hábrók access nodes on the night of 2026-04-29, prevented new jobs from starting in any queue and disabled the web portal. On 2026-04-30, we applied mitigating measures that prevent this vulnerability from being exploited. All idle nodes were immediately patched and rebooted and a mitigating measure that blocks the vulnerability was applied to nodes that still had jobs running, to prevent malicious code from being executed until they are rebooted with a patch. Due to this, these nodes won't accept new jobs and will reboot as soon as they are empty. 
 +  * As of 16:30 the access nodes are available again, the queues are resumed, and users can access the system as usual. Capacity will be reduced until all nodes have finished rebooting. 
 +  * You can follow the timeline of this incident on our [[https://status.hpc.rug.nl/issue/ba5f9dc4-bfb1-4910-aa78-1ff715e551af|status page issue]].
 +
 +===== 2026-04-13 =====
 +
 +  * ''interactive1.hb.hpc.rug.nl'' needed to be reinstalled after a failure. This means its ssh host key has changed. See [[hostkey_fingerprints]] for more information about host keys.
 +
 +===== 2026-02-27 =====
 +
 +  * New GPU nodes have been made available. See [[..:advanced_job_management:rtx_pro_6000_gpu_nodes]] for details.
 +  * The default number of threads for OpenBLAS and MKL has been set to 1. This to prevent their automatic parallelization to interfere with the parallelization of the software using these libraries. See [[..:advanced_job_management:blas_threads]] for details.
 +
 +===== 2026-02-18 =====
 +
 +  * The [[..:connecting_to_the_system:web_portal|]] has been updated from Open OnDemand v4.0.1 to Open OnDemand v4.1.0.
 +
 +===== 2026-01-26 =====
 +
 +  * Similarly to what was done on 2026-01-06, the memory of the compute nodes was again reduced slightly because the issue was not resolved yet. This means that you may need to adjust your memory request if you want to use all available memory on a node.
  
 ===== 2026-01-06 ===== ===== 2026-01-06 =====
  
   * The memory on the compute nodes available to jobs has been reduced to prevent nodes from running out of memory. This caused system services to crash, causing issues on affected nodes. This means that you may need to adjust your memory request if you want to use all available memory on a node.   * The memory on the compute nodes available to jobs has been reduced to prevent nodes from running out of memory. This caused system services to crash, causing issues on affected nodes. This means that you may need to adjust your memory request if you want to use all available memory on a node.
 +  * The nodes bought by GELIFES are out of support and as such the ''gelifes'' partition has been decommissioned.
  
 ===== 2025-10-24 ===== ===== 2025-10-24 =====