Error LCMVROPSYSTEM25016 when replacing certificate due to external CSR generation - VMware VCF Operations

Products

• VCF Operations

Issue/Introduction

This article provides remediation steps for certificate import failures (LCMVROPSYSTEM25016) in VMware Cloud Foundation (VCF) Operations caused by missing private key associations.

The certificate replacement workflow in VCF Operations fails with following error:

• LCMVROPSYSTEM25016
• certificate.error.ERROR-6: "No private key is found in the file"

The certificate being imported was requested using an external tool (e.g., Aria Suite Lifecycle Manager) rather than natively within VCF Operations.

Environment

VMware Cloud Foundation (VCF) 9.0.x and later.

Cause

Generating a Certificate Signing Request (CSR) in an external tool (e.g., Aria Suite Lifecycle Manager) results in a mismatch because the corresponding private key is not stored in the VCF Operations local database.

Resolution

To ensure proper private key alignment within the local database, generate the Certificate Signing Request (CSR) natively within VCF Operations:

1. Log in to the VCF Operations Product UI.

2. Navigate to Manage > Fleet Management > Certificates.

3. Click Generate CSR directly within the VCF Operations interface.

4. Submit the generated CSR to your Certificate Authority (CA) for signing.

5. Complete the certificate replacement process using the signed certificate derived from this native CSR. Refer steps from KB: Error LCMVROPSYSTEM25016 when attempting to use Replace With Imported Certificate flow in VCF Operations