Repository navigation
Commit f68b443
fix(validator): say why host driver validation failed
When the host has nvidia-smi but it cannot talk to the driver (for
example after the driver packages were upgraded without a reboot, so
the user-space libraries and the loaded kernel module differ), the
driver-validation init container logs:
No pre-installed driver detected on the host: exit status 18
...
failed to validate the driver, retrying after 5 seconds\n
and then retries the driver container path forever. Both lines point
away from the real problem: a driver is installed on the host, and the
retry warning never says what failed (it also prints a literal "\n").
- validateHostDriver: when nvidia-smi was found on the host but failed
to run, return an error that says so and names the binary.
- runValidation: log "No usable pre-installed driver detected" instead
of "No pre-installed driver detected".
- validateDriverContainer: include the error in the retry warning and
drop the trailing "\n".
No change in control flow.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: YoungjuKim <[email protected]>1 parent dbb11e8 commit f68b443
1 file changed
Lines changed: 9 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
745 | 745 | | |
746 | 746 | | |
747 | 747 | | |
748 | | - | |
| 748 | + | |
| 749 | + | |
| 750 | + | |
| 751 | + | |
| 752 | + | |
| 753 | + | |
| 754 | + | |
749 | 755 | | |
750 | 756 | | |
751 | 757 | | |
| |||
794 | 800 | | |
795 | 801 | | |
796 | 802 | | |
797 | | - | |
| 803 | + | |
798 | 804 | | |
799 | 805 | | |
800 | 806 | | |
| |||
809 | 815 | | |
810 | 816 | | |
811 | 817 | | |
812 | | - | |
| 818 | + | |
813 | 819 | | |
814 | 820 | | |
815 | 821 | | |
| |||
0 commit comments