As per PR "
Remediate the host and check the value for Login Timeout of the host and the value seems to be updated
Run compliance check on the host again and it fails with error "The advanced parameter LoginTimeout for discovery configuration 10.102.17.50:3260 for iSCSI Adapter vmhba64 has a different value than one configured in the profile"The compliance check error post this can be ignored.To reproduce the issue:
Extract host profile from a host
Edit the host profile and change the Login timeout value of one iSCSI target to a fixed value and leave the rest to default on the profile
Save the changes
Attach host profile to the same host and run a compliance check
Compliance check as expected fails with error "The advanced parameter LoginTimeout for discovery configuration 192.168.1.101:3260 for iSCSI Adapter vmhba64 has a different value than one configured in the profile"
Remediate the host and check the value for Login Timeout of the host and the value seems to be updated
Run compliance check on the host again and it fails with error "The advanced parameter LoginTimeout for discovery configuration 192.168.1.101:3260 for iSCSI Adapter vmhba64 has a different value than one configured in the profile"
Look onto the 'Settable' column in the below esxcli output:
Impact/Risks:
No impact