VCF Operations for Networks upgrade precheck fails with "An unexpected error occurred in step check_precheck_binaries_availability."
search cancel

VCF Operations for Networks upgrade precheck fails with "An unexpected error occurred in step check_precheck_binaries_availability."

book

Article ID: 447188

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite) VCF Operations for Networks

Issue/Introduction

  • While attempting to upgrade VCF Operations for Networks (formerly VMware Aria Operations for Networks) to version 9.1, the upgrade precheck fails during the binary availability validation phase.
  • The precheck results display the following error: An unexpected error occurred in step check_precheck_binaries_availability. Reference Code: 84AC3E7E. Detail: Failed to resolve binary URL from source: https://<sddc_manager_fqdn>/depot-service/content-gateway/PROD/COMP/VRNI/VCF-Operations-for-networks-9.1.#.#.######-update-manifest.json
  • Attempts to validate or update the Software Depot connection fail with: Error occurred on the authorization server. Please try again. Reference token: BB65QQ
  • Messages similar to the following are seen in the Software depot logs (on a VCF Management Services worker node, under /var/log/containers/depot-service-####_vcf-fleet-depot_download-service-################.log:

    2026-07-06T21:14:33.712849981Z stdout F 2026-07-06T21:14:33.712+0000 ERROR [download_service,0000000000000000,0000] [o.a.c.c.C.[.[.[.[dispatcherServlet],https-jsse-nio-0.0.0.0-8443-exec-7] Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed: com.vmware.evo.sddc.lcm.depot_auth.exceptions.DepotAccessTokenParseException: Unparsable JSON response from Broadcom oAuth authorization server. HTTP Status code: 407; Headers: [Mime-Version: 1.0, Date: Mon, 06 Jul 2026 16:16:26 CDT, Via: 1.1 <proxy server FQDN/IP>:<proxy server port> (Cisco-WSA/14.5.1-016), Content-Type: text/html, Proxy-Authenticate: Negotiate, Proxy-Authenticate: NTLM, Proxy-Authenticate: Basic realm="########", Connection: close, Proxy-Connection: close, Content-Length: 2193], Body: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

Environment

  • VCF 9.1
  • VCF Operations for Networks 9.x
  • Proxy server with authentication is configured

Cause

The password for the user associated with the proxy server configuration was recently changed and the new password was not configured for VCF Management Services.

Resolution

The steps at Configure a Proxy Server for VCF Management Services Components and VCF Automation can be used to update the proxy server configuration. 

On Step 6, the only parameter that needs to be passed in the JSON body is

    "peerProxy": {
      "password": "<new password>"
    }

Powered by Wolken Software