<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label. For the Community Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug For the Enterprise Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Kubernetes integration works but Helm Tiller fails to install on arm64 cluster with : > Something went wrong while installing Helm Tiller > > Operation failed. Check pod logs for install-helm for more details. Checking the logs I see > standard_init_linux.go:207: exec user process caused "exec format error" ### Steps to reproduce Install kubernetes onto an arm64 device and set up kubernetes integration via gitlab. When you go to install apps on it click the `Install` button next to `Helm Tiller`. Watch it fail. Note that helm can be installed on that cluster manually with `snap install helm --classic` and `helm init` runs successfully so this appears to be a gitlab issue. ### Example Project (If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, 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 is fixed in a more recent version) ### What is the current *bug* behavior? Helm fails to install. ### What is the expected *correct* behavior? Helm should install ### Relevant logs and/or screenshots ara@jetson-nano:~$ kubectl logs -n gitlab-managed-apps install-helm helm standard_init_linux.go:207: exec user process caused "exec format error" ### 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.6.3p62 Gem Version: 2.7.9 Bundler Version:1.17.3 Rake Version: 12.3.2 Redis Version: 3.2.12 Git Version: 2.21.0 Sidekiq Version:5.2.7 Go Version: unknown GitLab information Version: 12.0.2 Revision: 1a9fd38a4ca Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 10.7 URL: https://ago-git.us.ara.com HTTP Clone URL: https://ago-git.us.ara.com/some-group/some-project.git SSH Clone URL: git@ago-git.us.ara.com:some-group/some-project.git Using LDAP: yes Using Omniauth: yes Omniauth Providers: GitLab Shell Version: 9.3.0 Repository storage paths: - default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell 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 subtasks ... Checking GitLab Shell ... GitLab Shell: ... GitLab Shell version >= 9.3.0 ? ... OK (9.3.0) 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 Gitaly ... Gitaly: ... default ... OK Checking Gitaly ... Finished Checking Sidekiq ... Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1 Checking Sidekiq ... Finished Checking Incoming Email ... Incoming Email: ... Reply by email is disabled in config/gitlab.yml Checking Incoming Email ... Finished Checking LDAP ... ** I'm ommitting these ** Checking LDAP ... Finished Checking GitLab App ... 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: ... 5/1 ... yes 10/4 ... yes 10/5 ... yes 11/6 ... yes 11/7 ... yes 11/8 ... yes 10/9 ... yes 14/10 ... yes 10/11 ... yes 11/12 ... yes 11/13 ... yes 11/14 ... yes 15/15 ... yes 12/16 ... yes 14/17 ... yes 10/18 ... yes 10/21 ... yes 10/22 ... yes 11/23 ... yes 21/24 ... yes 10/26 ... yes 10/27 ... yes 14/29 ... yes 10/30 ... yes 14/31 ... yes 10/32 ... yes 10/33 ... yes 14/34 ... yes 23/35 ... yes 11/38 ... yes 11/39 ... yes 11/40 ... yes 14/44 ... yes 10/45 ... yes 14/46 ... yes 11/47 ... yes 21/49 ... yes 21/52 ... yes 21/53 ... yes 21/54 ... yes 14/55 ... yes 21/56 ... yes 29/57 ... yes 16/59 ... yes 21/60 ... yes 16/61 ... yes 3/63 ... yes 16/67 ... yes 16/68 ... yes 16/69 ... yes 32/71 ... yes 33/73 ... yes 33/74 ... yes 33/75 ... yes 33/76 ... yes 34/77 ... yes 33/78 ... yes 10/79 ... yes 34/80 ... yes 34/81 ... yes 34/82 ... yes 34/83 ... yes 34/84 ... yes 34/85 ... yes 11/86 ... yes 11/87 ... yes 11/88 ... yes 21/89 ... yes 29/90 ... yes 29/91 ... yes 33/92 ... yes 35/93 ... yes 35/94 ... yes 36/95 ... yes 21/96 ... yes 16/97 ... yes 39/98 ... yes 39/99 ... yes 33/100 ... yes 21/101 ... yes 21/102 ... yes 10/103 ... yes 39/104 ... yes 39/105 ... yes 39/106 ... yes 39/107 ... yes 33/108 ... yes 16/109 ... yes 16/111 ... yes 16/112 ... yes 16/113 ... yes 10/114 ... yes 29/115 ... yes 11/116 ... yes 29/117 ... yes 16/119 ... yes 29/120 ... yes 11/122 ... yes 11/123 ... yes 14/124 ... yes 11/125 ... yes 3/126 ... yes 38/127 ... yes 38/128 ... yes 38/129 ... yes 38/130 ... yes 35/131 ... yes 35/132 ... yes 35/133 ... yes 35/134 ... yes 29/138 ... yes 28/139 ... yes 28/140 ... yes 12/141 ... yes 38/142 ... yes 38/143 ... yes 28/146 ... yes 28/147 ... yes 29/150 ... yes 29/151 ... yes 29/152 ... yes 29/153 ... yes 10/154 ... yes 21/155 ... yes 28/156 ... yes 28/157 ... yes 28/158 ... yes 28/159 ... yes 29/161 ... yes 42/162 ... yes 11/163 ... yes 11/166 ... yes 29/169 ... yes 29/170 ... yes 29/171 ... yes 10/172 ... yes 29/173 ... yes 29/174 ... yes 29/175 ... yes 29/176 ... yes 29/177 ... yes 29/178 ... yes 29/179 ... yes 29/180 ... yes 28/182 ... yes 28/183 ... yes 29/184 ... yes 29/185 ... yes 29/186 ... yes 24/187 ... yes 48/188 ... yes 48/189 ... yes 17/190 ... yes 29/191 ... yes 24/192 ... yes 29/193 ... yes 48/194 ... yes 29/195 ... yes 3/196 ... yes 29/197 ... yes 24/198 ... yes 24/199 ... yes 29/200 ... yes 29/201 ... yes 48/202 ... yes 24/203 ... yes 42/204 ... yes 29/205 ... yes 29/207 ... yes 48/208 ... yes 29/209 ... yes 29/210 ... yes 29/211 ... yes 29/212 ... yes 48/213 ... yes 3/214 ... yes 29/216 ... yes 29/217 ... yes 29/218 ... yes 48/219 ... yes 3/220 ... yes 3/221 ... yes 3/222 ... yes 3/223 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.5.3 ? ... yes (2.6.3) Git version >= 2.21.0 ? ... yes (2.21.0) Git user has default SSH configuration? ... no Try fixing it: mkdir ~/gitlab-check-backup-1562100252 sudo mv /var/opt/gitlab/.ssh/authorized_keys.lock.old ~/gitlab-check-backup-1562100252 For more information see: doc/ssh/README.md in section "SSH on the GitLab server" Please fix the error above and rerun the checks. Active users: ... 11 Checking GitLab App ... Finished Checking GitLab subtasks ... Finished </pre> </details> ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)