top of page

Experienced Technology Product Manager adept at steering success throughout the entire product lifecycle, from conceptualization to market delivery. Proficient in market analysis, strategic planning, and effective team leadership, utilizing data-driven approaches for ongoing enhancements.

  • Twitter
  • LinkedIn
White Background

vRealize Automation 8.1 P3 deploy.sh is failing with Error: cannot connect to Tiller

Updated: Jan 16, 2021


Deploying vRealize Automation 8.1 P3 fails at the "checking helm version" step with the error: cannot connect to Tiller.


This issue occurs because the tiller is running on a single vRA node in the case of vRA HA. However, if the deploy.sh is run from a node different than the tiller node, the helm requests will timeout and the deploy.sh will fail.


Workaround


Download the file attached below


2672731-add-tiller-proxy.tar
.gz
Download GZ • 2KB

On only one of the vRA nodes, upload the "2672731-add-tiller-proxy.tar.gz" file in "/root"


Run this command


tar -xvf 2672731-add-tiller-proxy.tar.gz && chmod a+x 2672731-add-tiller-proxy.sh && ./2672731-add-tiller-proxy.sh && rm 2672731-add-tiller-proxy.*

Run the "helm ls" command from all vRA nodes to confirm that helm can be reached from all vRA nodes




172 views0 comments

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page