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

Increasing the disk space for the VMware vCenter Server Appliance in vSphere 6.5, 6.7 and 7.0

  Purpose This article provides steps to increase the disk space of a specific VMDK for the vCenter Server Appliance 6.5, 6.7 and 7.0. With the introduction of Logical Volume Management (LVM) in vSphere 6.0 and continued support with vSphere 6.5, 6.7 and 7.0, the vCenter Server disks can be dynamically increased. List of VMDKs for a vCenter Server Appliance 6.5 - Size Mount point and Purpose Note : Resizing the root partition (VMDK1 listed in the KB above) is not supported on 6.5. Please see the vSphere 6.5 Release Notes for more information. Resizing root partition has been added to 6.7 and 7.0. List of VMDKs/Partitions for a vCenter Server Appliance 6.7 - Size Mount point and Purpose   List of VMDKs/Partitions for a vCenter Server 7.0 - Size Mount point and Purpose Note : This KB can be used for the situation like SEAT partition full or any other vCenter appliance partition full. ...
Post a Comment
Read more

Cloning and converting virtual machine disks with vmkfstools

 Purpose This article provides information and instructions on the use of the vmkfstools command to convert virtual machine disks from one type to another. Resolution The vmkfstools command offers the ability to clone virtual machine content and also convert from one virtual machine disk ( .vmdk ) format into another. Note : The host operating system chosen to perform the conversion may not necessarily support running of virtual machines via the output format defined. vmkfstools maintains the possibility of exporting virtual disks for use in other VMware products which support alternative disk formats. To convert a virtual machine disk from one type to another: Shut down the virtual machine. Virtual machine disk files are locked while in-use by a running virtual machine. Log in to the VMware vSphere Management Assistant (v...
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