Error: 'Log management was not discovered with the provided import details' during upgrade to Log Management 9.1.0

Products

• VCF Operations

Issue/Introduction

Upgrade from VCF Operations for Logs 9.0.2 to Log Management 9.1.0 fails. The following errors are observed on the upgrade Task in the UI during the upgrade process:

Error: Validate component specifications before installation
Error: Log management was not discovered with the provided import details.
Error: Step deploy_ops_logs_cluster failed. Reference Code: #######. Check logs for details.

Environment

VCF Operations 9.1

VCF Operations for logs 9.0.x

Cause

VCF Operations for Logs 9.0 was imported with incorrect details (such as being deployed on an incorrect network where validation checks did not block it). As a result, the component successfully installed and appears in the Fleet LCM UI, but it is not operable. During the upgrade to version 9.1, the system fails to discover Log Management using the provided import details.

Resolution

To resolve this issue, clear the stuck component using the Fleet LCM API and initiate a new deployment:

Stage 1: Deregister the Component from Fleet LCM

Step 1: Acquire VSP_TOKEN

curl -k --request POST --url https://<VSP_ADDRESS>/api/v1/identity/token --header 'content-type: application/x-www-form-urlencoded' --data grant_type=password --data [email protected] --data 'password=<VSP_ADMIN_PASSWORD>'

Where: VSP_ADDRESS is the address of the VSP hosting the fleet LCM. VSP_ADMIN_PASSWORD is the password of the vmware-system-user for the given VSP.

Step 2: Identify the Component ID(s) to Delete

curl -k -X GET "https://<FLEET_FQDN>/fleet-lcm/v1/components?includeConsumptionVsp=true&includeVcdMigrator=true" \
  -H "Authorization: Bearer $VSP_TOKEN" -v

Where FLEET_FQDN is the FQDN of the Fleet Lifecycle component. This can be found in the VCF Operations UI by browsing to the Build >> Lifecycle >> VCF Management >> Components tab.

Tip: Copy the output into a notepad and search for the string "componentType": "OPS_LOGS", COMPONENT_ID is the ID mentioned 2 lines above this string.

Step 3: Delete the Relevant Components

curl -X DELETE "https://<FLEET_FQDN>/fleet-lcm/v1/components/<COMPONENT_ID>" \
  -k -H "Authorization: Bearer $VSP_TOKEN"

Stage 2: Remove the component from upgrade plan (if applicable)

1. SSH to the VCF service runtime control plane node using the IP found in the Build >> Lifecycle >> VCF Management >> Components >> VCF Service Runtime page. Username is vmware-system-user.
2. Elevate the permissions to root using the command:

   sudo su

3. Set kubeconfig and access the database:

   export KUBECONFIG=/etc/kubernetes/admin.conf

4. Connect to the master database pod:

   kubectl exec -it vcf-fleet-lcm-db-0 -n vcf-fleet-lcm -- psql -U postgres -d vcffleetlcmdb

5. Delete the upgrade plan component (replace <COMPONENT_ID> with the component ID used above):

   delete from upgrade_plan_component where component_id='<COMPONENT_ID>';

Stage 3: Re-deployment

1. Use the Add Component button for Log Management in the components page, which will no longer be grayed out.
2. Initiate the deployment using the old cluster primary FQDN and provide the new 9.1 Log Management FQDN.

Note: While configurations will automatically sync from the 9.0.2 instance to the 9.1 instance, historical data will not. Customers must manually migrate historical data using the Broadcom utility once deployment completes as mentioned in the Log Data Transfer documentation.

Additional Information

For defects and enhancements, subscribe to this article (reference: Article 275360) to be updated on fix status.