CI: restart task-runner after helm deployment

Restart the task-runner pod of the helm release, after wait_for_deploy.

Our task runner often uses an outdated image in dev, as there is nothing
day-to-day, to cause the pod to be restarted, (even though a new
task-runner latest image is created at least nightly). This isn't a
problem in a production environment, because the images are tagged with
versions, and the version change is enough to cause restarts when needed.

Closes #1593
16 jobs for 1593-restart-task-runner-after-deploy in 93 minutes and 47 seconds (queued for 4 minutes and 50 seconds)
Status Job ID Name Coverage
  Prepare
passed #347340939
check_docs_lint

00:00:51

passed #347340937
danger-review

00:00:49

 
  Review
passed #347340941
review_eks

00:09:10

passed #347340940
review_gke

00:10:48

passed #347340943
allowed to fail manual
stop_review_eks

00:00:33

passed #347340942
allowed to fail manual
stop_review_gke

00:00:38

 
  Specs
passed #347340945
review_specs_eks

00:08:31

passed #347615674
review_specs_gke

00:10:50

failed #347340944
review_specs_gke

00:07:55

 
  Qa
passed #347340947
debug_review

00:00:48

failed #347661601
allowed to fail
qa_eks

01:00:01

failed #347661607
allowed to fail
qa_gke

01:00:01

passed #347340946
review_helm_test

00:00:26

failed #347340949
allowed to fail
qa_eks

01:00:05

failed #347340948
allowed to fail
qa_gke

01:00:05

 
  Package
passed #347340950
lint_package

00:00:51

 
Name Stage Failure
failed
qa_gke Qa The script exceeded the maximum execution time set for the job
$ source "${VARIABLES_FILE}"
$ app_version=$(ruby -e "require 'yaml'; puts YAML.safe_load(File.read('Chart.yaml'))['appVersion']")
$ qa_version="nightly"
$ if [ "$app_version" != "master" ]; then
$ GITLAB_USERNAME=root GITLAB_PASSWORD=$ROOT_PASSWORD GITLAB_ADMIN_USERNAME=root GITLAB_ADMIN_PASSWORD=$ROOT_PASSWORD EE_LICENSE=$REVIEW_APPS_EE_LICENSE gitlab-qa Test::Instance::Any EE:$qa_version https://$QA_ENVIRONMENT_URL
Running test suite `Test::Instance::All` for gitlab-ee
Docker shell command: `docker run -t --rm --net=bridge --env GITLAB_ADMIN_USERNAME="$GITLAB_ADMIN_USERNAME" --env GITLAB_ADMIN_PASSWORD="$GITLAB_ADMIN_PASSWORD" --env GITLAB_USERNAME="$GITLAB_USERNAME" --env GITLAB_PASSWORD="$GITLAB_PASSWORD" --env GITHUB_ACCESS_TOKEN="$GITHUB_ACCESS_TOKEN" --env GITLAB_URL="$GITLAB_URL" --env EE_LICENSE="$EE_LICENSE" --env CI="$CI" --env CI_NODE_TOTAL="$CI_NODE_TOTAL" --env GITLAB_CI="$GITLAB_CI" --volume /var/run/docker.sock:/var/run/docker.sock:z --volume /builds/gitlab-org/charts/gitlab/gitlab-qa-run-2019-11-11-21-31-32-e7ff9db1/gitlab-ee-qa-988cf6fd:/home/gitlab/qa/tmp:z --name gitlab-ee-qa-988cf6fd gitlab/gitlab-ee-qa:nightly Test::Instance::All https://gitlab-gke-review-1593-r-jg4h3r.helm-charts.win`
Pulling docker image gitlab/gitlab-runner-helper:x86_64-b295d93b ...
ERROR: Job failed: execution took longer than 1h0m0s seconds
failed
qa_eks Qa The script exceeded the maximum execution time set for the job
alpine: Pulling from gitlab/gitlab-runner
Digest: sha256:883e7a072cfa94da5908b6a07fc538c55fda999d1405bed875f5edd91cb8c19c
Status: Image is up to date for gitlab/gitlab-runner:alpine
Executing `docker network inspect test`
[]
Error: No such network: test
Executing `docker run -d --rm --entrypoint=/bin/sh --network bridge --name qa-runner-1573508137 -p 8093:8093 -e CI_SERVER_URL=https://gitlab-eks-review-1593-r-n950r9.eks.helm-charts.win -e REGISTER_NON_INTERACTIVE=true -e REGISTRATION_TOKEN=FJswkNDM1qzr7pMmb-AD -e RUNNER_EXECUTOR=shell -e RUNNER_TAG_LIST=qa,test -e RUNNER_NAME=qa-runner-1573508137 gitlab/gitlab-runner:alpine -c "printf 'concurrent = 1\ncheck_interval = 0\n\n[session_server]\n session_timeout = 1800' > /etc/gitlab-runner/config.toml && gitlab-runner register --run-untagged=false && gitlab-runner run " `
Pulling docker image gitlab/gitlab-runner-helper:x86_64-b295d93b ...
ERROR: Job failed: execution took longer than 1h0m0s seconds