Attempting the remediation for Image Compliance under Auto Deploy fails with "Cannot complete login due to an incorrect user name or password"
search cancel

Attempting the remediation for Image Compliance under Auto Deploy fails with "Cannot complete login due to an incorrect user name or password"

book

Article ID: 408423

calendar_today

Updated On:

Products

VMware vCenter Server VMware vCenter Server 8.0

Issue/Introduction

  • While performing remediation of Cluster Image Compliance for Auto Deploy host, the task may fail with "Cannot complete login due to an incorrect user name or password"

  • /var/log/vmware/rbd/rbd-syslog.log

YYYY-MM-DDTHH:MM:SS [1024169:BulkRemediateMapping-task-<PID>]ERROR:rule_set:bulk remediation failed:(vim.fault.InvalidLogin) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
msg = 'Cannot complete login due to an incorrect user name or password.',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) []
}
Traceback (most recent call last):
File "bora/install/vmvisor/autodeploy/site-packages/vmware/rbd/vmodl_impl/rule_set.py", line 29, in _bulkRemediateMapping
File "bora/install/vmvisor/autodeploy/site-packages/vmware/rbd/vmodl_impl/rule_set.py", line 155, in RemediateMapping
pyVmomi.VmomiSupport.vim.fault.InvalidLogin: (vim.fault.InvalidLogin) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
msg = 'Cannot complete login due to an incorrect user name or password.',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) []

  • /var/log/vmware/vpxd/vpxd.log

YYYY-MM-DDTHH:MM:SS error vpxd[1017409] [Originator@6876 sub=Default opID=63460af] [VpxLRO] -- ERROR lro-15102 -- 52cae3ca-b462-4a18-b4e5-e6cb459cf89c(525313d3-b223-af63-7cbc-74b2ddd56d8b) -- SessionManager -- vim.SessionManager.impersonateUser: :vim.fault.InvalidLogin
--> Result:
--> (vim.fault.InvalidLogin) {
-->    faultCause = (vmodl.MethodFault) null, 
-->    faultMessage = <unset>
-->    msg = ""
--> }
--> Args:
--> 
--> Arg userName:
--> "autodeploy-########-####-####-####-############"
--> Arg locale:
--> 

Cause

This issue is caused due to the default localos domain being missing under the Identity Source of the vCenter server. The user names without domain are considered as members of default domain which by default is localos domain.

Resolution

Proceed to recreate the localos identity source on the vCenter Server

  • Log in to vCenter Server using vSphere Client
  • Click on the hamburger icon and navigate as below

Click Administration > Single Sign On > Configuration > Identity Provider > Identity Sources > ADD

  • Select Local operating system of SSO server in the Identity Source Type dropdown menu and enter the Name as localos and click ADD.