Error when deploying VCF Management Services during VCF 9.1 upgrade - VCF Instance Cloud Proxy Registration validation failed
search cancel

Error when deploying VCF Management Services during VCF 9.1 upgrade - VCF Instance Cloud Proxy Registration validation failed

book

Article ID: 443889

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • During the VCF 9.1 upgrade, while deploying VCF Management Services, when click "Install" - the following error is returned - 

VCF Instance Cloud Proxy Registration validation failed

  • The SDDC Manager log /var/log/vmware/vcf/domainmanager/domainmanager.log contains an entry - 

YYYY-MM-DDThh:mm:ss.sss+0000 DEBUG [vcf_dm,xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx,xxxx] [c.v.e.s.c.v.util.ResponseUtil,dm-exec-xxx]  Build validation response: {"errorCode":"BROWNFIELD_VCF_INSTANCE_CLOUD_  
PROXY_REGISTRATION_VALIDATION.error","arguments":[],"context":{"severity":"ERROR","bundleName":"com.vmware.evo.sddc.common.validation.errors.messages","validation.taskId":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"},"message":"VCF Instance Cloud Proxy Registration validation failed","remediationMessage":"Verify VCF Instance Cloud Proxy Registration is properly configured"}

Environment

VCF 9.1.0.0

Cause

  • The SDDC Manager first logs into the primary VCF Operations analytics cluster
  • It then retrieves the inventory, after which it discovers the registered Cloud Proxy and attempts to validate communication with it
  • VCF Operations was still assigned to the default analytics cluster Collector Group, thus the validation fails

Resolution

  • To resolve the validation error being encountered -
    • Log into VCF Operations UI > Administration > Integrations page
    • Edit the VMware Cloud Foundation infrastructure account
    • Under the VCF Credentials section - there is a "Cloud Proxy / Group" drop down menu
    • Change the setting from the entry under the "Default Group" to the dedicated Cloud Proxy appliance under the "Ungrouped Collectors" list
    • Clicked Save
  • Retry the previously failing workflow
  • The issue is then expected to have been resolved