Error: "Vdcupgrade failed. Error[9234] - User invalid credential" upgrading to PSC 6.5

Products

• VMware vCenter Server

Issue/Introduction

• Upgrading to Platform Services Controller 6.5 fails with the error:
  
  Encountered an internal error. see /var/log/firstboot/vmafd-firstboot.py_xxx_stderr.log.
   
• In the vmafd-firstboot.py_xxx_stderr.log file, you see entries similar to:
   
  YYYY-MM-DDTHH:MM:SS.140Z password:
  YYYY-MM-DDTHH:MM:SS.140Z Vdcupgrade failed. Error[9234] - User invalid credential
   
  YYYY-MM-DDTHH:MM:SS.140Z <type 'exceptions.SystemExit'>
  YYYY-MM-DDTHH:MM:SS.140Z <type 'exceptions.SystemExit'>
   
• In the upgrade-source-requirements.log file, you see entries similar to:
   

  YYYY-MM-DDTHH:MM:SS.228Z INFO sso_connector SSO https port is configured to: 443

  YYYY-MM-DDTHH:MM:SS.234Z ERROR bindings.sso_binding Cannot log-in to SSO admin service, because of Error: (vmodl.fault.InvalidRequest) {

  dynamicType = <unset>,

  dynamicProperty = (vmodl.DynamicProperty) [],

  msg = "Request version 'urn:sso/version3_5' and namespace 'urn:sso' are not supported",

  faultCause = <unset>,

  faultMessage = (vmodl.LocalizableMessage) []

  }.

  Traceback (most recent call last):

  File "/tmp/vmware-root/tmpvmware236/py/bindings/sso_binding.py", line 138, in createSession

  content = si.RetrieveServiceContent()

  File "/tmp/vmware-root/tmpvmware236/libs/pyVmomi.zip/pyVmomi/VmomiSupport.py", line 557, in <lambda>

  self.f(*(self.args + (obj,) + args), **kwargs)

  File "/tmp/vmware-root/tmpvmware236/libs/pyVmomi.zip/pyVmomi/VmomiSupport.py", line 363, in _InvokeMethod

  return self._stub.InvokeMethod(self, info, args)

  File "/tmp/vmware-root/tmpvmware236/libs/pyVmomi.zip/pyVmomi/SoapAdapter.py", line 1335, in InvokeMethod

  raise obj # pylint: disable-msg=E0702

  vmodl.fault.InvalidRequest: (vmodl.fault.InvalidRequest) {

  dynamicType = <unset>,

  dynamicProperty = (vmodl.DynamicProperty) [],

  msg = "Request version 'urn:sso/version3_5' and namespace 'urn:sso' are not supported",

  faultCause = <unset>,

  faultMessage = (vmodl.LocalizableMessage) []

  }

  YYYY-MM-DDTHH:MM:SS.236Z WARNING bindings.sso_binding Could not retrieve service instance from SSO component using API version 'sso.version.version3_5'. Falling back to API version 'sso.version.version1'.

   
• In the firstbootInfrastructure.log file, you see entries similar to:
   

  YYYY-MM-DDTHH:MM:SS.257Z INFO firstbootInfrastructure Running firstboot script: ['/opt/vmware/bin/python', '/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py', '--action', 'firstboot']

  YYYY-MM-DDTHH:MM:SS.147Z INFO firstbootInfrastructure [Failed] /usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py is complete

  YYYY-MM-DDTHH:MM:SS.148Z INFO firstbootInfrastructure No localized error detail found in /var/log/firstboot/vmafd-firstboot.py_60570_stderr.log, assuming internal error

  YYYY-MM-DDTHH:MM:SS.149Z WARNING firstbootInfrastructure Bug component info file does not exist

  YYYY-MM-DDTHH:MM:SS.149Z INFO firstbootInfrastructure Firstboot duration: 53 sec

  YYYY-MM-DDTHH:MM:SS.149Z INFO firstbootInfrastructure First boot is a failure
   

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

• VMware vCenter Server Appliance 6.0.x
• VMware vCenter Server Appliance 6.7.x
• VMware vCenter Server Appliance 6.5.x

Cause

This issue occurs due to bad SSO password.

Resolution

1. Change the SSO password to a supported password. For more information, see vCenter Single Sign-On password policy.
2. Restart the upgrade process.