Hostprofile compliance fails with error "Host does not appear to have a compliant stateless cache."
search cancel

Hostprofile compliance fails with error "Host does not appear to have a compliant stateless cache."

book

Article ID: 395353

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Host compliance for newly auto deployed hosts with stateless caching fails with the following in /var/run/log/syslog.log :

    YYYY-MM-DDTHH:MM:SSZ In(14)[+] hostprofile[4276811]:    key = 'com.vmware.vim.profile.caching.stateless.caching.esx.not.found',
    YYYY-MM-DDTHH:MM:SSZ In(14)[+] hostprofile[4276811]:    arg = (vmodl.KeyAnyValue) [],
    YYYY-MM-DDTHH:MM:SSZ In(14)[+] hostprofile[4276811]:    message = 'Host does not appear to have a compliant stateless cache.'
    YYYY-MM-DDTHH:MM:SSZ In(14)[+] hostprofile[4276811]: }].^@
    YYYY-MM-DDTHH:MM:SSZ Er(11) hostprofile[4276811]: opID=m6ggxsg5-8742063-auto-57df5-h5:##-6f-WorkQueue-94cdbe3-1b-a2cd: systemCache_caching_CachingProfileExpression:systemCache_caching_CachingProfile-ProfExpression failed compliance test^@

    YYYY-MM-DDTHH:MM:SSZ In(14) HostProfileManager[4276537]: m6ggxsg5-8741227-auto-57cup-h5:###-1b-01-76-a24c: runcommand called with: args = '/bin/lsof > /tmp/openfile-before-unmount.txt', outfile = None, returnoutput = True, timeout = 0.0.^@
    YYYY-MM-DDTHH:MM:SSZ Er(11) dcbd[2100033]: [error]    set_hw_pg: Failed status(195887136)
    YYYY-MM-DDTHH:MM:SSZ Er(11) hostprofile[4276537]: opID=m6ggxsg5-8741227-auto-57cup-h5:###-1b-01-76-a24c: Exception while applying host config. Exception: ("Errors: \nVolume '67e####1-#######-####-c4####e50ee' cannot be unmounted. Reason: Busy\n", b'')^@
    YYYY-MM-DDTHH:MM:SSZ Wa(12) hostprofile[4276537]: opID=m6ggxsg5-8741227-auto-57cup-h5:####-1b-01-76-a24c: Exception while applying host config. Backtrace:

  • /var/run/log/vmkernel.log report nsx/nestdb services still writing to the volume being unmounted in syslog.log :

    2025-04-03T19:51:40.625Z Wa(180) vmkwarning: cpu21:2112479)WARNING: VC: 2445: unmounting opened volume ('67e####1-#######-####-c4####e50ee' 'OSDATA-67e####1-#######-####-c4####e50ee') with ref 5 is not allowed.
    2025-04-03T19:51:40.626Z In(182) vmkernel: cpu21:2112479)FSS: 9834: File nsx-ods.log, fhID: 351293, is opened by world: 000002109176 - nsx-sha
    2025-04-03T19:51:40.626Z In(182) vmkernel: cpu21:2112479)FSS: 9834: File metrics_1743709500.log, fhID: 351825, is opened by world: 000002108204 - nestdb-server
    2025-04-03T19:51:40.626Z In(182) vmkernel: cpu21:2112479)VC: 2716: Unmount volume f533 28 2 67e####1 ####### #### c4####e50ee 4 1 0 0 0 0 0 : Busy

Cause

 

  1. OSData Partition in Use: The OSData partition is actively used, preventing unmounting.

  2. Hardcoded Log Path: The log file location is hardcoded to a specific partition, which contributes to the issue.

Resolution

Currently, this is a known issue. Please reach out to Broadcom Support if service still writing to the volume is nsx or nestdb.

Additional Information

Powered by Wolken Software