After upgrade to 10.0.1, Gitlab Shell Runner fails with connection reset by peer

After upgrading from 9.5.1, our gitlab shell runners can no longer clone remote repos. These failures occur with 9.x and 10.0 runners. The error messages look like:

fatal: unable to access 'https://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@gitlab.myco.com/my-proj/orchestrator.git/': TCP connection reset by peer

We can manually curl the affected urls by forcing TLS 1.2 but are unsure how to convince the shell runner to also use TLS 1.2 when cloning repos.

The runners are currently execluted from and OEL 7.4 host.

This is was resolved by re-enabling tls 1.1 support in /etc/gitlab/gitlab.rb as documented here: https://about.gitlab.com/2017/09/22/gitlab-10-0-released/#tlsv1-no-longer-accepted-by-default