[Bug]: Precompiled node pools drop kernels that sanitize to the same name
维护者通常 1 天内回复
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 20/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 停滞
- 技术栈
- go, kubernetes
调研方向
Read internal/state/nodepool.go and the existing TestGetSanitizedKernelVersion test. Run the reported command, go test -count=1 -run TestGetNodePoolsKeepsPrecompiledKernelsThatSanitizeTogether ./internal/state/, to see the failing case. Done means nodes with the same raw kernel share a pool, while kernels that sanitize to the same name get separate pools with their own selectors and image tags; a linked pull request is already open.
由索引模型根据 Issue 内容生成。
描述
Describe the bug
With spec.usePrecompiled: true, getNodePools keeps one node pool per sanitized kernel name. getSanitizedKernelVersion strips x86_64, aarch64, and an optional _64k. Two nodes whose raw feature.node.kubernetes.io/kernel-version.full values differ only by architecture or page size collapse into one pool.
The surviving pool's node selector and driver image tag use the first node's raw kernel. The other nodes get no driver DaemonSet. The NVIDIADriver can still become Ready.
This was found by reading internal/state/nodepool.go on main (operator v26.7.2). It is not a live cluster repro.
To reproduce
From the code path. TestGetSanitizedKernelVersion already expects these two strings to become 5.14.0-427.37.1.el9.4:
5.14.0-427.37.1.el9_4.x86_645.14.0-427.37.1.el9_4.aarch64
Put one GPU node on each kernel, with the same OS, under one NVIDIADriver that sets usePrecompiled: true.
On current main, getNodePools returns one pool. The unit test is:
go test -count=1 -run TestGetNodePoolsKeepsPrecompiledKernelsThatSanitizeTogether ./internal/state/
That test fails with 1 pool instead of 2.
Expected behavior
One pool per raw kernel. Nodes with the same raw kernel still share a pool. The sanitized name can stay shared. The selector and the image tag for each pool must keep that pool's own raw kernel.
I will open a pull request with that change.
- 主要语言
- Go
- 星标
- 2.9k
- 派生
- 582
- 平均合并
- 2 天 2 小时
- 30 天内合并 PR
- 57
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
NVIDIA/gpu-operator 的其他 Issue
-
[Bug]: dcgm-exporter no longer gets hostNetwork when a host DCGM is set through dcgmExporter.env可能已有人在做 @blacksoxx 于 4 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 64/100
NVIDIA/gpu-operator#3091 ·
维护者通常 1 天内回复
-
feature lifecycle/frozen needs-triage
难度 2/5 1-3 小时 新手友好度 68/100
NVIDIA/gpu-operator#3074 · 2 条评论 ·
维护者通常 1 天内回复
-
[Bug]: GPUCluster common name label breaks DRA validator selector可能已有人在做 @ajavanma 于 30 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
NVIDIA/gpu-operator#2955 · 1 条评论 ·
维护者通常 1 天内回复
-
[Bug]: ClusterPolicy reconcile panics when a DaemonSet has no annotations可能已有人在做 @SebTardif 于 3 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 25/100
NVIDIA/gpu-operator#3096 · 3 条评论 ·
维护者通常 1 天内回复
-
[Bug]: driver-validation hides why a pre-installed driver failed and loops without a reason可能已有人在做 @fjvbn2003 于 7 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 25/100
NVIDIA/gpu-operator#3085 ·
维护者通常 1 天内回复
查看 NVIDIA/gpu-operator 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
-
status:needs-review type:bug
难度 2/5 1-3 小时 新手友好度 78/100
Gentleman-Programming/engram#2079 ·
维护者通常 1 天内回复
-
bug triage/pending
难度 1/5 1 小时以内 新手友好度 66/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
limitlessprojects/Go-Hybrid#1377 ·
维护者通常 1 天内回复
-
bug report
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 3 天内回复