• Arun Nukula

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

Updated: 3 days ago


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




2 views0 comments

Subscribe Now

  • Twitter
  • Facebook Social Icon

Copyright © 2019 nukescloud