Yesterday I spun my wheels a bit on an issue I encountered whilst trying to deploy vRealize Suite Life Cycle Manager (vRSLCM) via the vRealize Easy Installer. I downloaded the ISO, opened it up, navigated to the vrlcm-ui-installer folder and clicked on the installer.exe. I selected the Install option, then went through the steps to roll-out the vRSLCM product, as shown below.
Almost immediately on completing the deployment I hit this error: “Failed to send http data”:
I examined the logs and this is what I found:
2020-07-13T13:49:45.201Z - info: output:PROGRESS 2020-07-13T13:49:50.307Z - info: output: 2020-07-13T13:49:50.310Z - info: output: ERROR + <Errors> + <Error> + <Type>ovftool.http.send</Type> + <LocalizedMsg> + Failed to send http data + </LocalizedMsg> + </Error> + </Errors> 2020-07-13T13:49:57.350Z - info: output:RESULT + ERROR 2020-07-13T13:49:57.353Z - error: Ovf Service:vmrefFlag: false 2020-07-13T13:49:57.353Z - info: Cancelling timeout due to error from progress callback 2020-07-13T13:49:57.354Z - error: Progress Controller: [VCSA ERROR] - Progress callback error 2020-07-13T13:49:57.354Z - error: Progress Controller: [VCSA ERROR] - Details Failed to send http data 2020-07-13T13:49:57.361Z - info: Cancelling the ping timer for session mgmt 2020-07-13T13:49:57.361Z - info: Cancelling the ping timer for session mgmt 2020-07-13T13:49:57.385Z - info: ovfProcess child process exited with code 1 2020-07-13T13:50:04.757Z - info: Exiting from the app
It turns out that this is a bug in the version of ovftool bundled with the Easy Installer. It seems that it is having difficulties doing DNS lookups. The workaround is to add the entries for the vCenter server and ESXi hosts to your local hosts file. The issue is described in the vRealize Automation product documentation. This also made it into KB article 78541.