"Failed to find product type for id 789" when upgrading to VCF 5.2 with offline bundle utility.
search cancel

"Failed to find product type for id 789" when upgrading to VCF 5.2 with offline bundle utility.

book

Article ID: 374197

calendar_today

Updated On:

Products

VMware Cloud Foundation 5.x

Issue/Introduction

Receive the following precheck error after uploading the 5.2 VCF bundles with the offline bundle utility.

Bundle Transfer Utility fails to upload the NSX Advanced Load Balancer install bundle

Environment

VMware Cloud Foundation 5.x

Cause

The NSX Advanced Load Balancer is only supported in VCF 5.2 or greater. 

Resolution

Upgrade SDDC to 5.2 before uploading the NSX Advanced Load Balancer bundle.

Workaround:

1. Take a snapshot of the SDDC Manager VM. 
2. SSH into the SDDC VM and elevate to root.

3. Disable Depot polling if environment is connected to the internet/depot.

a. Edit the application-prod.properties file

vi /opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties

b. Set lcm.core.enableVmwareCompatibilityDataPolling to false.

example: lcm.core.enableVmwareCompatibilityDataPolling=false

c. Cycle the lcm service for the change to take effect. 

systemctl restart lcm

4. Create a copy of the VVS data json.

cp /nfs/vmware/vcf/nfs-mount/compatibility/VmwareCompatibilityData.json /nfs/vmware/vcf/nfs-mount/compatibility/VmwareCompatibilityData.json-bkp

5. Remove the NSX Advanced Load Balancer from the VVS data. 

jq 'walk(if type == "object" and .productId == 789 then empty else . end)'  /nfs/vmware/vcf/nfs-mount/compatibility/VmwareCompatibilityData.json-bkp >  /nfs/vmware/vcf/nfs-mount/compatibility/VmwareCompatibilityData.json

6. After successfully upgrading SDDC Manager to 5.2 enable the VmwareCompatibilityDataPolling (If applicable)

a. Edit the application-prod.properties file

vi /opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties

b. Set lcm.core.enableVmwareCompatibilityDataPolling to true.

example: lcm.core.enableVmwareCompatibilityDataPolling=true

c. Cycle the lcm service for the change to take effect. 

systemctl restart lcm

Additional Information