UnabletoCheckCompliance" under the Hosts > Configure > Host Profile tab.You need to set host customizations before proceeding with host remediation./var/run/log/syslog.log will show entries similar to:Er(11) hostprofile[123456]: opID=######-######-auto-#####-h5:########-e4-WorkQueue-######-##-####: Failed with invalid IP address ##.##.##.## Er(11)[+] hostprofile[123456]: Traceback (most recent call last):Er(11)[+] hostprofile[123456]: File "/lib64/python3.11/site-packages/hostprofiles/pyEngine/nodeputil.py", line 90, in IsValidIpv4AddressEr(11)[+] hostprofile[123456]: OSError: illegal IP address string passed to inet_aton^@Er(11) hostprofile[123456]: opID=######-######-auto-#####-h5:########-e4-WorkQueue-######-##-####: Failed to parse address ##.##.##.## Er(11)[+] hostprofile[123456]: Traceback (most recent call last):Er(11)[+] hostprofile[123456]: File "/lib64/python3.11/site-packages/hostprofiles/pyEngine/nodeputil.py", line 129, in IsValidIpv6AddressEr(11)[+] hostprofile[123456]: File "/lib64/python3.11/socket.py", line 974, in getaddrinfoEr(11)[+] hostprofile[123456]: socket.gaierror: [Errno -2] Name or service not known^@
vCenter Server 8.Xx
vSphere ESXi 8.x
An IP address entry within the Host Profile configuration contains a trailing space, causing the validation engine to treat the integer-based IP as an invalid string.
Log in to the vSphere Client.
Navigate to Policies and Profiles > Host Profiles.
Select the affected Host Profile and click Edit Settings.
Search for the IP address identified in the syslog.
Remove any trailing or leading spaces from the IP address field.
Save the Host Profile.
Re-run the compliance check and proceed with remediation.