Skip to content

[Fix] fix kmm build when builder scheduled to node with different kernel#50

Merged
sajmera-pensando merged 1 commit intoROCm:mainfrom
yansun1996:netop_66_main
Feb 11, 2026
Merged

[Fix] fix kmm build when builder scheduled to node with different kernel#50
sajmera-pensando merged 1 commit intoROCm:mainfrom
yansun1996:netop_66_main

Conversation

@yansun1996
Copy link
Member

Motivation

Fix the builder pod failure when builder was assigned to a worker node that has different kernel version compared to builder's target kernel version.

Technical Details

In network operator's dockerfile we're using KERNEL_FULL_VERSION instead of KERNEL_VERSION to inject the kernel version

the Dockerfile is using the wrong ENV in some lines, making those ENV empty value.

In that case if the builder pod got scheduled to a node with different kernel version to build the driver, it would fail.

In this PR it is correcting the ENV name to make sure the right kernel version was injected to all the lines of dockerfile

In that way, the build process would keep working regardless of builder container's host node kernel version.

Test Plan

Test Result

Submission Checklist

Copy link
Collaborator

@sundar-pds sundar-pds left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@sajmera-pensando sajmera-pensando merged commit 7e94c1c into ROCm:main Feb 11, 2026
2 checks passed
@yansun1996 yansun1996 deleted the netop_66_main branch February 12, 2026 01:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants