Unable to Upgrade VCF Operations from 9.0.2 to 9.1 Due to Cloud Proxy Validation
search cancel

Unable to Upgrade VCF Operations from 9.0.2 to 9.1 Due to Cloud Proxy Validation

book

Article ID: 443797

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

When attempting to upgrade VMware Cloud Foundation (VCF) Operations from version 9.0.2 to version 9.1, the upgrade process fails during the pre-validation phase with error "VCF Instance Cloud Proxy Registration validation failed" and code "BROWNFIELD_VCF_INSTANCE_CLOUD_PROXY_REGISTRATION_VALIDATION.error".

Environment

VCF Operations 9.1

Cause

The upgrade pre-validation performs a strict check to ensure that all deployed Cloud Proxy collectors are in a "Unified" state. If the environment contains legacy or non-unified Cloud Proxies registered to the VCF Operations instance, this validation check fails, halting the upgrade process.

Resolution

Ideally, all Cloud Proxy collectors should be updated to the Unified state prior to the upgrade. However, if this is not immediately possible, you can apply a workaround to bypass this specific validation check and proceed with the 9.1 upgrade.
Workaround Procedure:
  1. Log in to SDDC Manager: Access the SDDC Manager appliance via SSH using the vcf user credentials. (Note: Once logged in, switch to the root user (using su -) to ensure you have the necessary permissions to edit system files).
  2. Edit the Configuration File: Open the application.properties file using a text editor such as vi
     
    vi /etc/vmware/vcf/domainmanager/application.properties
    
  3. Append the Flag: Add the following line to the very bottom of the properties file to disable the validation check:
    validation.disable.validate.brownfield.vcf.instance.cloud.proxy.registration=true
    
  4. Save and Close: Save the changes to the file and exit the text editor
  5. Retry Upgrade: Return to the SDDC Manager UI and re-initiate the upgrade plan. The pre-validation check for the Cloud Proxy registration state will now be bypassed, allowing the upgrade from 9.0.2 to 9.1 to proceed successfully.