Deploying VCF Operations for Logs failing with error code “LCMVRLICONFIG40119” at stage 13

Products

• VCF Operations

Issue/Introduction

• Failed deployment task error message:
  
  LCMVRLICONFIG40119
Error occurred while pushing capabilities to VCF Ops Logs, statusCode : 500 : {"errorMessage":"Could not save configuration"} : {"errorMessage":"Could not save configuration"}
  
  
• VCF Management > Components (tab) page lists "operations" component as "Pending Import" with button under "Action" column for "IMPORT".
  

Environment

VCF 9.x

Cause

VCF Operations component had not completed final steps of “Import” into Fleet Manager.

Resolution

Proceed with “Import” of VCF Ops nodes as this required post step has not yet been completed.

• This leaves the Ops VMs on the legacy VC to be manually transferred at a desired later time.

• Once the Operations component shows completed successfully (e.g., "Status: New Deployment", "Action: Manage") retry failed Operations for Logs deployment task.
  • To retry the task do the following:
    1. Navigate to VCF Management > Tasks (tab)
    2. Find the deployment task that failed and select it.
    3. Click the "Retry" button at the bottom of the window.

Additional Information

Other articles that may be relevant if you experience issues importing the "Operations" component or continue having issues deploying Ops for Logs.

• Unable to add VCF Operations for logs and VCF Operations in Fleet management as vCenter Server List is empty
• How to reset the root password in Cloud proxy
• Failure while deploying or performing inventory sync for Ops for Logs 9.x - LCMVRLICONFIG40119
• How to replace a corrupted truststore in VCF Operations for Logs