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'
Tanzu Hub
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.
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.
By using the manual process, the platform will not attempt to upload an incompatible vSphere stemcell.