Installing helm on existing Kubernetes cluster fails with non-specific error (#25035) · Issues · GitLab.org / GitLab

Installing helm on existing Kubernetes cluster fails with non-specific error

### Summary While attempting to add an 'existing' k8 cluster (fresh Rancher 2.0 install, in this case. Also happens with OpenShift Origin as well as OpenShift Online) the process will fail when installing Helm with a non-specific error: `Something went wrong while installing Helm Tiller Kubernetes error.` gitlab-rails/production.log doesn't contain anything useful. ### Steps to reproduce Add k8s cluster via Project->Operations->Kubernetes->Existing Cluster. Save settings and click 'Install' next to Helm Tiller to install Helm Tiller into cluster. ### Example Project (If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, and link to it here in the bug report) (If you are using an older version of GitLab, this will also determine whether the bug has been fixed in a more recent version) ### What is the current *bug* behavior? Non-specific error when installing Helm Tiller ### What is the expected *correct* behavior? Either correctly installing Helm Tiller or a bug that contains some information I can leverage to fix the issue so that Helm can be installed ### Relevant logs and/or screenshots **Error in UI** ![Gitlab-k8s_error](/uploads/b882da25a9c77e1798dcc48d8e8cdf8a/Gitlab-k8s_error.PNG) **gitlab-rails/production.log** ``` Started POST "/<user>/<project>/clusters/6/applications/helm" for <ip> at 2018-11-05 09:03:13 -0500 Processing by Projects::Clusters::ApplicationsController#create as JSON Parameters: {"namespace_id"=>"<user>", "project_id"=>"<project>", "id"=>"6", "application"=>{}} Completed 204 No Content in 32ms (ActiveRecord: 6.7ms) Started GET "/-/metrics" for 127.0.0.1 at 2018-11-05 09:03:14 -0500 Processing by MetricsController#index as HTML Completed 200 OK in 16ms (Views: 0.9ms | ActiveRecord: 0.0ms) Started GET "/<user>/<project>/clusters/6/status.json" for <ip> at 2018-11-05 09:03:20 -0500 Processing by Projects::ClustersController#status as JSON Parameters: {"namespace_id"=>"<user>", "project_id"=>"<project>", "id"=>"6"} Completed 200 OK in 39ms (Views: 0.5ms | ActiveRecord: 5.7ms) Started GET "/-/metrics" for 127.0.0.1 at 2018-11-05 09:03:29 -0500 Processing by MetricsController#index as HTML Completed 200 OK in 20ms (Views: 1.2ms | ActiveRecord: 0.0ms) Started GET "/<user>/<project>/clusters/6/status.json" for <ip> at 2018-11-05 09:03:30 -0500 Processing by Projects::ClustersController#status as JSON Parameters: {"namespace_id"=>"<user>", "project_id"=>"<project>", "id"=>"6"} Completed 200 OK in 40ms (Views: 0.6ms | ActiveRecord: 5.5ms) ``` This has also been [reported by others on the gitlab subreddit](https://www.reddit.com/r/gitlab/comments/9odxjg/gitlab_autodevops_kubernetes_managed_by_rancher/) ### Output of checks (If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com) #### Results of GitLab environment info <details> <summary>Expand for output related to GitLab environment info</summary> <pre> System information System: Ubuntu 18.04 Current User: git Using RVM: no Ruby Version: 2.4.5p335 Gem Version: 2.7.6 Bundler Version:1.16.2 Rake Version: 12.3.1 Redis Version: 3.2.12 Git Version: 2.18.1 Sidekiq Version:5.2.1 Go Version: go1.10.4 linux/amd64 GitLab information Version: 11.4.5 Revision: f5536c61210 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql URL: https://git.local.trincoll.edu HTTP Clone URL: https://git.local.trincoll.edu/some-group/some-project.git SSH Clone URL: git@git.local.trincoll.edu:some-group/some-project.git Using LDAP: no Using Omniauth: yes Omniauth Providers: saml GitLab Shell Version: 8.3.3 Repository storage paths: - default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git </pre> </details> #### Results of GitLab application Check <details> <summary>Expand for output related to the GitLab application check</summary> <pre> Checking GitLab Shell ... GitLab Shell version >= 8.3.3 ? ... OK (8.3.3) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:root, or git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... 13/1 ... ok 2/2 ... ok 2/3 ... ok 5/4 ... ok 13/5 ... ok 5/6 ... ok 5/8 ... ok 14/9 ... ok 14/10 ... ok 14/11 ... ok 8/12 ... ok Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful Checking GitLab Shell ... Finished Checking Sidekiq ... Running? ... yes Number of Sidekiq processes ... 1 Checking Sidekiq ... Finished Reply by email is disabled in config/gitlab.yml Checking LDAP ... LDAP is disabled in config/gitlab.yml Checking LDAP ... Finished Checking GitLab ... Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 13/1 ... yes 2/2 ... yes 2/3 ... yes 5/4 ... yes 13/5 ... yes 5/6 ... yes 5/8 ... yes 14/9 ... yes 14/10 ... yes 14/11 ... yes 8/12 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.4.5) Git version >= 2.9.5 ? ... yes (2.18.1) Git user has default SSH configuration? ... yes Active users: ... 9 Checking GitLab ... Finished </pre> </details> ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

issue