You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
False-negative driver cert when host reports driver version but no driver name #47
Running against a live ESXi 9.1 host, a RAID controller shows driver_certified: "N/A" even though its current_driver_version clearly matches an entry in supported_drivers (seen via -json):
The host's 90.4900.0.5000 matches the HCL base version 90.4900.0.5000 (from 90.4900.0.5000-3vmw.910), so this is a false-negative.
Root cause
For RAID/SAS/block HBAs on ESXi 9.1+, driver version + firmware are pulled via the raw SOAP call in parseHBAFirmwareFromSOAP (vsphere.go), which extracted firmwareVersion and driverVersion but not the <driver> (module name) element. So driver_name came back empty.
The matcher in hcl.go (evaluateVsanPCI) gated driver certification on the driver name — both the CertFalse baseline (DriverName != "" && DriverVer != "") and the version comparison (strings.Contains(res.DriverName, drvName)). With an empty name, the version comparison never ran, leaving the result at N/A.
Fix
Extract the <driver> module name in parseHBAFirmwareFromSOAP and carry it into the RAID/block HBA entries so driver_name is populated.
Add a version-only fallback in the matcher: when the host reports a driver version but no name, judge certification by matching the version against the device's already-PCI-matched supported drivers. Name matching stays enforced when a name is present (no blanket pass).
Activity
Never report a CPU as uncertified when its CPUID is unavailable (#62)
Never report a CPU as uncertified when its CPUID is unavailable (#62)