Replacing certificate for VCF components fails with error "Environment Not found"

Products

• VCF Operations

Issue/Introduction

• Attempting the 'Replace with Configured CA Certificate' on VCF Operations UI under Fleet Management -> Certificates for any VCF component results in the following error banner to appear in the Fleet Manager UI:
  

  Certificate replacement for appliance <fqdn> has failed. 500 : "{"status":"","message":"Environment Not found","errorCode":"LCM_CERTIFICATE_API_ERROR0005","errorLabel":null,"recommendations":[]}"

   

• On the Fleet Manager, the /var/log/vrlcm/vmware_vrlcm.log file reports the following error:
  

  ERROR vrlcm[#] [http-nio-8080-exec-#] [c.v.v.l.l.c.CertificateStoreController] – Environment Not found
  com.vmware.vrealize.lcm.common.exceptions.CertificateReadException: Environment Not found

Environment

VMware Cloud Foundation 9.x

Cause

The error occurs because the certificate reference for the target environment is temporarily out of sync within the Fleet Manager inventory database.

Because the Fleet Manager cannot map the correct environment reference, the API request to replace the certificate fails with an 'Environment Not found' exception.

Resolution

Currently, the issue resolves through automated backend synchronization.

1. Allow Background Synchronization:
   Wait for 24 hours to allow the Fleet Manager appliance to automatically update and synchronize certificate references.
   
   
2. Retry the Operation:
   After the 24-hour synchronization period has passed, navigate back to the Fleet Manager UI and retry the 'Replace with Configured CA' action for the VCF Component.

Note: If the issue persists after 24 hours, ensure that appliances are properly communicating and that there are no underlying network or NTP (time synchronization) issues preventing the automated inventory update. Reach out to Broadcom Support for further investigation if the issue remains unresolved.