Error: 'Failed to stage the VCF Component' during VCF Automation upgrade staging

Products

• VCF Automation

Issue/Introduction

When upgrading VCF Automation (VCFA) to version 9.1, the staging task for the upgrade bundle on the consumption cluster fails mid-transit.

Symptoms:

• The UI displays the error: Failed to stage the VCF Component.

• The stage component task terminates with the string (can be checked using the export KUBECONFIG=/etc/kubernetes/admin.conf and kubectl get bundle -A commands): stream error: stream ID 1; INTERNAL_ERROR; received from peer.

• Workflow pod logs (can be checked using the kubectl get pods -A | grep precheck then kubectl logs -n vmsp-platform component-action-stage-precheck-<id of the pod that is in Error state> commands) show "URL is not reachable: <URL>. HTTP status: 500. Please verify the URL and network connectivity" even though the URL is reachable.

• Testing the curl -o test.tar <URL captured from the above error> -k command fails exactly after downloading 9.96 GB with curl: (18) end of response with <5GB in bytes> bytes missing error.

• The connection terminates consistently once the data transfer reaches 10GB.

Environment

VCF Automation 9.1

Cause

The network proxy host restricts the maximum amount of data allowed per connection or request to a threshold (10GB) lower than the size of the upgrade package tar bundle (15GB).

Resolution

1. Update the proxy configuration: On the proxy host, increase or remove the Maximum amount of data per connection or request limit to allow transfers exceeding 15GB.

2. Clean up the initial failed upgrade attempt by running the environment manual rollback procedures on the fleet side. Refer to Failed component cleanup during VCF 9.1 installation or upgrade.

3. If the upgrade precheck fails with error com.broadcom.vcfa.upgrade.90.application.check.test-application-01-9x-fips, apply the approved workaround configuration to skip this specific check. Refer to VCF Automation Upgrade to 9.x Fails FIPS Precheck Due to Incorrectly Configured Integration Endpoints.

4. Re-run the upgrade prechecks to verify they pass, and proceed with completing the upgrade execution.