VCF deployment using Cloud Builder failed at Uploading vSAN HCL to SDDC Manager

Products

VMware SDDC Manager VMware Cloud Foundation

Issue/Introduction

VCF deployment using Cloud Builder failed at Uploading vSAN HCL to SDDC Manager

/var/log/vmware/vcf/bringup/vcf-bringup.log shows the below error

YYYY-MM-DDTHH:MM:SS.414+0000 [bringup,xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx,d2d4] ERROR [c.v.e.s.s.UploadVsanHclToSddcManagerAction,pool-2-thread-13] Failed to upload HCL on SDDC Manager.
YYYY-MM-DDTHH:MM:SS.414+0000 [bringup,xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx,d2d4] ERROR [c.v.e.s.o.model.error.ErrorFactory,pool-2-thread-13] [IQEAE1] UPLOADING_HCL_TO_SDDC_MANAGER_FAILED Uploading vSAN HCL to SDDC Manager Failed
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Uploading vSAN HCL to SDDC Manager Failed
					at com.vmware.evo.sddc.sddcmanager.UploadVsanHclToSddcManagerAction.execute(UploadVsanHclToSddcManagerAction.java:105)
					at com.vmware.evo.sddc.sddcmanager.UploadVsanHclToSddcManagerAction.execute(UploadVsanHclToSddcManagerAction.java:48)
					at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.invoke(FsmActionState.java:62)
					at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:159)
					at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:144)
					at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.invokeMethod(ProcessingTaskSubscriber.java:400)
					at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.processTask(ProcessingTaskSubscriber.java:520)
					at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:124)
					at jdk.internal.reflect.GeneratedMethodAccessor253.invoke(Unknown Source)
					at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
					at java.base/java.lang.reflect.Method.invoke(Method.java:568)
					at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:85)
					at com.google.common.eventbus.Subscriber.lambda$dispatchEvent$0(Subscriber.java:71)
					at com.vmware.vcf.common.tracing.TraceRunnable.run(TraceRunnable.java:59)
					at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
					at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
					at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: org.springframework.web.client.HttpClientErrorException: 413 Request Entity Too Large: "<html><EOL><EOL><head><title>413 Request Entity Too Large</title></head><EOL><EOL><body><EOL><EOL><center><h1>413 Request Entity Too Large</h1></center><EOL><EOL><hr><center>nginx</center><EOL><EOL></body><EOL><EOL></html><EOL><EOL>"

Environment

VMware Cloud Foundation

Cause

The all.json file is too large than the allowed upload limit of 40MB

Resolution

Re-download the all.json file by following the steps below, upload to the SDDC Manager and proceed further.

Open the below link in your HTML browser:
- https://partnerweb.vmware.com/service/vsan/all.json (Right click, Save as).
- Save the file as all.json on your local machine. If you are unable to save the file, you must copy the entire content and create a new file with extension".json"
Copy the latest all.json file from your local machine to /home/vcf folder onto your sddc manager via tools like WinSCP.

Update the deployment Parameters with the below mentioned path under Path to HCL JSON File.

Use the below command to grab the access token

curl --location 'https://<sddcmanager_fqdn>/v1/tokens' --header 'Content-Type: application/json' --data-raw '{"username":"<SSO_USERNAME>","password":"<SSO_PASSWORD>"}'

cd to /home/vcf (where the latest local copy of all.json is placed)

Upload the HCL file using the HCL upload API using the below command

curl -X PUT --location 'http://<sddcmanager_fqdn>/v1/vsan-hcl/content' --header 'Authorization: Bearer <put the token grabbed from step 3>' --header 'Content-Type: text/plain' [email protected]

Retry the Cloud Builder deployment.