Automated Foundation Attach fails in Tanzu Hub with 422 Unprocessable Entity
search cancel

Automated Foundation Attach fails in Tanzu Hub with 422 Unprocessable Entity

book

Article ID: 438612

calendar_today

Updated On:

Products

VMware Tanzu Platform Core

Issue/Introduction

When attempting to use the Automated Attach workflow in Tanzu Hub to connect a Public Cloud based foundations(AWS,GCP,Azure), the process fails during the stemcell upload stage.

The following error is observed in the logs:

[INFO] Upload stemcell to Foundation Core started for stemcell: bosh-stemcell-xxx-vsphere-esxi-ubuntu-jammy-go_agent.tgz
[ERROR] Failed to upload StemCell bosh-stemcell-xxx-vsphere-esxi-ubuntu-jammy-go_agent.tgz to OpsManager: Streaming upload failed: 422 Unprocessable Entity from POST https://<opsman-url>/api/v0/stemcells
[ERROR] Upload stemcell failed: message='Streaming upload failed: 422 Unprocessable Entity from POST https://<opsman-url>/api/v0/stemcells', type='java.lang.RuntimeException: Streaming upload failed: 422 Unprocessable Entity from POST https://<opsman-url>/api/v0/stemcells'

Environment

Tanzu Hub

Cause

The Automated Attach workflow is currently designed and hardcoded for vSphere environments.

When this workflow is initiated, the system automatically downloads a vSphere-specific stemcell (e.g., bosh-stemcell-*-vsphere-esxi-*) and attempts to upload it to the target Operations Manager. Because a public cloudbased Operations Manager is configured with respective BOSH CPI, it rejects the vSphere stemcell, resulting in the 422 Unprocessable Entity HTTP error.

Resolution

Automated attachment for public cloud foundations (GCP, AWS, Azure) is not supported at this time. To connect a such foundations to the Tanzu Hub, you must use the Manual Attach workflow.

Workaround Steps

  1. Log in to the Tanzu Hub console.
  2. Navigate to the area where you manage or add foundations.
  3. Initiate the attachment process but select Manual Attach instead of Automated.
  4. Provide the required manual configuration details, such as:
    • Ops Manager URL
    • Authentication credentials/passcode
  5. Complete the wizard to finish the attachment.

By using the manual process, the platform will not attempt to upload an incompatible vSphere stemcell.