Skip to content

[state-driver] check driver daemons startup status through sentinel file - #2727

Open
tariq1890 wants to merge 1 commit into
mainfrom
daemons-status-file
Open

[state-driver] check driver daemons startup status through sentinel file#2727
tariq1890 wants to merge 1 commit into
mainfrom
daemons-status-file

Conversation

@tariq1890

@tariq1890 tariq1890 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

This change is accompanied by the driver-container PR NVIDIA/gpu-driver-container#913.

We introduce a new sentinel file called .driver-daemons-status which will help the driver container ensure that the Fabric Manager and other daemons are all fully up and running before the driver container goes into the Running state.

For reasons of backward compatibility, we only enforce this check if the .driver-daemons-status file is present. This way, the operator will continue to work with other driver containers that don't have this capability

@coveralls

coveralls commented Aug 10, 2026

Copy link
Copy Markdown

Coverage Status

coverage: 38.385% (-0.08%) from 38.466% — daemons-status-file into main

@tariq1890 tariq1890 self-assigned this Aug 10, 2026
@tariq1890
tariq1890 force-pushed the daemons-status-file branch from 531948c to 48b5707 Compare August 11, 2026 00:19
@shivamerla

Copy link
Copy Markdown
Contributor

looks good to me!

Comment thread assets/state-driver/0400_configmap.yaml Outdated
Signed-off-by: Tariq Ibrahim <tibrahim@nvidia.com>
@tariq1890
tariq1890 force-pushed the daemons-status-file branch from 48b5707 to d1c42d6 Compare August 11, 2026 16:07

@rahulait rahulait left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@rahulait

Copy link
Copy Markdown
Contributor

One quick question: what will happen if the user started with newer operator and newer driver image, then driver image wrote NotReady to that status file and fails to start the daemons correctly. If the user has to switch to an older image say which is working fine, will the operator be able to proceed in that case as the status file still exists on node with NotReady state? Or, will it be able to clear it and continue.

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.

4 participants