Applying host profile fails with error "Cannot apply the host configuration" due to invalid scratch config location

Products

• VMware vSphere ESXi
• VMware vSphere ESXi 8.0

Issue/Introduction

• Applying host profile fails with error "Cannot apply the host configuration".

• Following error in hostd.log:

YYYY-MM-DDTHH:MM:SS In(166) Hostd[2099019]: [Originator@6876 sub=Vimsvc.TaskManager opID=m8dns8mw-240665-auto-55px-h5:70028002-50-01-bc-edee sid=521c8a5c user=vpxuser:<no user>] Task Created : haTask--vim.profile.host.profileEngine.HostProfileManager.applyHostConfig-508

YYYY-MM-DDTHH:MM:SS Db(167) Hostd[2099007]: --> (vim.option.OptionValue) [

YYYY-MM-DDTHH:MM:SS Db(167) Hostd[2099007]: -->    (vim.option.OptionValue) {

YYYY-MM-DDTHH:MM:SS Db(167) Hostd[2099007]: -->       key = "ScratchConfig.ConfiguredScratchLocation",

YYYY-MM-DDTHH:MM:SS Db(167) Hostd[2099007]: -->       value = "/vmfs/volumes/Datastore_name"

YYYY-MM-DDTHH:MM:SS Db(167) Hostd[2099007]: -->    }

YYYY-MM-DDTHH:MM:SS Db(167) Hostd[2099007]: --> ]

YYYY-MM-DDTHH:MM:SS In(166) Hostd[2099050]: [Originator@6876 sub=Solo.Vmomi opID=m8dns8mw-240665-auto-55px-h5:70028002-50-01-bc-edee-ee2a sid=52e0b945 user=vpxuser] Throw vmodl.fault.InvalidArgument

YYYY-MM-DDTHH:MM:SS In(166) Hostd[2099050]: [Originator@6876 sub=Solo.Vmomi opID=m8dns8mw-240665-auto-55px-h5:70028002-50-01-bc-edee-ee2a sid=52e0b945 user=vpxuser] Result:

YYYY-MM-DDTHH:MM:SS In(166) Hostd[2099007]: --> (vmodl.fault.InvalidArgument) {

YYYY-MM-DDTHH:MM:SS In(166) Hostd[2099007]: -->    msg = "",

YYYY-MM-DDTHH:MM:SS In(166) Hostd[2099007]: --> }

YYYY-MM-DDTHH:MM:SS In(166) Hostd[2099034]: [Originator@6876 sub=Vimsvc.TaskManager opID=m8dns8mw-240665-auto-55px-h5:70028002-50-01-bc-edee-ee2e sid=52e0b945 user=vpxuser] Task Completed : haTask--vim.profile.host.profileEngine.HostProfileManager.applyHostConfig-508 Status error

 

 

Environment

VMware vSphere ESXi 7.x

VMware vSphere ESXi 8.x

Cause

This issue is due to mismatch between the host's current scratch space location and the one defined in the host profile.

Resolution

To resolve this follow the below steps:

1. Uncheck the scratch configuration from the existing host profile
2. Remediate the host