Skip to content

[DOC] Add know issue description for recent Device Plugin fix #410

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.

Sign up for GitHub

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
sajmera-pensando merged 1 commit into from
Jan 16, 2026
Merged

[DOC] Add know issue description for recent Device Plugin fix #410

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 2 additions & 0 deletions docs/releasenotes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,8 @@ The AMD GPU Operator v1.4.1 release extends platform support to OpenShift v4.20
- **Device Config Manager**
- Memory partition operations may occasionally fail due to leaked device handlers that prevent the amdgpu driver from being unloaded when applying a new memory partition profile. This issue has been observed on Debian 12 with MI325X GPU when using the v1.4.1 Device Config Manager.
- **Workaround:** Reboot the affected worker nodes and retry the partitioning operation.
- **Device Plugin**
- A regression was introduced in ROCm 7.0.1 corresponded amdgpu-dkms driver that may cause incorrect reporting of the total number of CPX partitioned GPUs. Users running Device Plugin images with versions earlier than 1.31.0.9 may be affected by this issue. To resolve this, please either re-pull the latest Device Plugin image or upgrade to Device Plugin version 1.31.0.9 or later.

## GPU Operator v1.4.0 Release Notes

Expand Down
Loading