Skip to main content

Firstboot Error: Failed to start Workload Control Plane Service

Symptoms

Upgrading from vCenter 6.7U3 to 7.0 GA and keep getting an error on Stage 2 of the upgrade:
An error occurred while starting service 'wcp'
Failed to start Workload Control Plane Service.

may see error like:

“An error occurred while invoking external command : 'Error 166 while adding user workload_storage_management-dc45c311-35e4-4ecd-a114-a52f0cb11e3d to SSO group "ServiceProviderUsers": dir-cli failed, error= Specified User or Group to be added doesn't exist. 100006 ' Failed to configure Workload Control Plane

Resolution: This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.”

Cause

Wcp.log

 

Starting service process with pid: 9662.

time="2020-05-07T14:33:45Z" level=info msg="Set debug mode to false"

time="2020-05-07T14:33:45Z" level=error msg="Encountered error when opening file /etc/vmware/wcp/.storageUser: open /etc/vmware/wcp/.storageUser: no such file or directory"

time="2020-05-07T14:33:45Z" level=error msg="Failed to parse Service Account data from file /etc/vmware/wcp/.storageUser: open /etc/vmware/wcp/.storageUser: no such file or directory"

time="2020-05-07T14:33:45Z" level=fatal msg="Failed to load storage service account from /etc/vmware/wcp/.storageUser, verify that firstboot succeeded"


The upgrade fails due to file storageUser not getting created
Resolution
-->take ssh to the newly created appliance
-->check under /etc/vmware/wcp if the file exists
->if not  create the file.

content of the file:
===========================================
workload_storage_management-3d2aab75-9f79-4c38-91e2-6cefc6727ba8
r"eH}W[5dKv+\OPas<CL
1589159830
==========================================

Comments

Post a Comment

Popular posts from this blog

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)   ...
Post a Comment
Read more

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive ...
Post a Comment
Read more

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...
Post a Comment
Read more