Skip to content

Updated hotfixes #1473

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 19, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/home/changelog/hotfixes-2-18.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,11 @@ The following is a list of the known and fixed issues for Run:ai V2.18.

| Internal ID | Hotfix # | Description |
| :---- | :---- | :---- |
| RUN-27640 | 2.18.104 | Fixed a security vulnerability in `github.com.golang-jwt.jwt.v5` related to CVE-2025-30204 with severity HIGH. |
| RUN-27893 | 2.18.104 | Fixed an issue where workloads submitted with an invalid node port range would get stuck in Creating status. |
| RUN-28006 | 2.18.104 | Fixed an issue where tokens became invalid for the API server after one hour. |
| RUN-27543| 2.18.104 | Fixed an issue where the GPU quota for a department could not be edited because the `maxAllowed` parameter was not updated when the over quota weight feature flag was turned off. |
| RUN-28097 | 2.18.104 | Fixed an issue where the `ALLOCATED_GPU_COUNT_PER_GPU` metric displayed incorrect data for fractional pods. |
| RUN-26359 | 2.18.102 | Fixed an issue in CLI v2 where using the `--toleration` option required incorrect mandatory fields. |
| RUN-26878 | 2.18.100 | Fixed an issue where, in some cases, previous inference request errors caused subsequent successful requests to report latency as NaN (Not a Number) instead of the actual value. As a result, these requests were not displayed in the UI latency graph, and the API returned NaN. |
| RUN-26800 | 2.18.99 | Fixed an issue where the `runai list nodes` command in CLI v1 did not display the correct number of free GPUs when using GPU memory. |
Expand Down
8 changes: 7 additions & 1 deletion docs/home/changelog/hotfixes-2-19.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,15 @@ The following is a list of the known and fixed issues for Run:ai V2.19.

| Internal ID | Hotfix # | Description |
| :---- | :---- | :---- |
| RUN-27295 | 2.19.113 | Fixed an issue in CLI v2 where the `--node-type` flag for inference workloads was not properly propagated to the pod specification. |
| RUN-27514 | 2.19.113 | Fixed an issue with incorrect calculation of the `ALLOCATED_CPU_MEMORY_BYTES` telemetry metric. |
| RUN-27521 | 2.19.113 | Fixed an issue where disabling CPU quota in the General settings did not remove existing CPU quotas from projects and departments. |
| RUN-27841 | 2.19.113 | Fixed an issue where workloads without a memory request failed validation in the workload-controller webhook. |
| RUN-27638 | 2.19.112 | Fixed a security vulnerability in `axios` related to CVE-2025-27152 with severity HIGH. |
| RUN-27867 | 2.19.112 | Fixed a security vulnerability in `github.com.golang.org.x.crypto` related to CVE-2025-22869 with severity HIGH. |
| RUN-27944 | 2.19.111 | Fixed a security vulnerability in `github.com.golang-jwt.jwt.v4` related to CVE-2025-30204 with severity HIGH. |
| RUN-26994 | 2.19.111 | Fixed an issue where session timeouts occurred when using the CLI. |
| RUN-28097 | 2.19.111 | Fixed an issue where the `allocated_gpu_count_per_gpu` metric displayed incorrect data for fractional pods. |
| RUN-28097 | 2.19.111 | Fixed an issue where the`ALLOCATED_GPU_COUNT_PER_GPU` metric displayed incorrect data for fractional pods. |
| RUN-27837 | 2.19.110 | Fixed an issue where a node pool’s placement strategy stopped functioning correctly after being edited. |
| RUN-27628 | 2.19.109 | Fixed an issue where a node pool could remain stuck in Updating status in certain cases. |
| RUN-27640 | 2.19.109 | Fixed a security vulnerability in `github.com.golang-jwt.jwt.v5` related to CVE-2025-30204 with severity HIGH. |
Expand Down
8 changes: 7 additions & 1 deletion docs/home/changelog/hotfixes-2-20.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,14 @@ This section provides details on all hotfixes available for version 2.20. Hotfix

| Version | Date | Internal ID | Description |
|--|--|--|--|
| 2.20.43 | 15/05/2025 | RUN-27295 | Fixed an issue in CLI v2 where the `--node-type` flag for inference workloads was not properly propagated to the pod specification. |
| 2.20.43 | 15/05/2025 | RUN-27375| Fixed an issue where projects were not visible in the legacy job submission form, preventing users from selecting a target project. |
| 2.20.43 | 15/05/2025 | RUN-27841 | Fixed an issue where workloads without a memory request failed validation in the workload-controller webhook. |
| 2.20.42 | 13/05/2025 | RUN-27514 | Fixed an issue with incorrect calculation of the `ALLOCATED_CPU_MEMORY_BYTES` telemetry metric. |
| 2.20.42 | 13/05/2025 | RUN-27521 | Fixed an issue where disabling CPU quota in the General settings did not remove existing CPU quotas from projects and departments. |
| 2.20.42 | 13/05/2025 | RUN-28380 | Fixed a security vulnerability in `github.com.golang.org.x.crypto` related to CVE-2025-22869 with severity HIGH. |
| 2.20.41 | 06/05/2025 | RUN-28241 | Fixed a security vulnerability in `github.com.golang-jwt.jwt.v5` related to CVE-2025-30204 with severity HIGH. |
| 2.20.41 | 06/05/2025 | RUN-28097 | Fixed an issue where the `allocated_gpu_count_per_gpu metric` displayed incorrect data for fractional pods. |
| 2.20.41 | 06/05/2025 | RUN-28097 | Fixed an issue where the `ALLOCATED_GPU_COUNT_PER_GPU` metric displayed incorrect data for fractional pods. |
| 2.20.41 | 06/05/2025 | RUN-28006 | Fixed an issue where tokens became invalid for the API server after one hour. |
| 2.20.41 | 06/05/2025 | RUN-27638 | Fixed a security vulnerability in axios related to CVE-2025-27152 with severity HIGH. |
| 2.20.40 | 30/04/2025 | RUN-27837 | Fixed an issue where a node pool’s placement strategy stopped functioning correctly after being edited.|
Expand Down