Running with gitlab-runner 13.1.0 (6214287e)
  on docker-auto-scale fa6cab46
section_start:1594395950:prepare_executor
Preparing the "docker+machine" executor
Using Docker executor with image registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.17.0 ...
Pulling docker image registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.17.0 ...
Using docker image sha256:f3e93bdc0fc2992fbc7a273e897f5f2f1d37c1a4e64cc3e5b53c5c9a1e73dc73 for registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.17.0 ...
section_end:1594396009:prepare_executor
section_start:1594396009:prepare_script
Preparing environment
Running on runner-fa6cab46-project-4422333-concurrent-0 via runner-fa6cab46-stg-srm-1594395950-1a52feda...
section_end:1594396012:prepare_script
section_start:1594396012:get_sources
Getting source from Git repository
$ eval "$CI_PRE_CLONE_SCRIPT"
Fetching changes with git depth set to 50...
Initialized empty Git repository in /builds/gitlab-org/monitor/monitor-sandbox/.git/
Created fresh repository.
Checking out 58558c76 as master...

Skipping Git submodules setup
section_end:1594396014:get_sources
section_start:1594396014:download_artifacts
Downloading artifacts
Downloading artifacts for dast_environment_deploy (37557109)...
Downloading artifacts from coordinator... ok        id=37557109 responseStatus=200 OK token=uKdfpr4L
section_end:1594396015:download_artifacts
section_start:1594396015:step_script
Executing "step_script" stage of the job script
$ auto-deploy check_kube_domain
$ auto-deploy download_chart
Creating /root/.helm 
Creating /root/.helm/repository 
Creating /root/.helm/repository/cache 
Creating /root/.helm/repository/local 
Creating /root/.helm/plugins 
Creating /root/.helm/starters 
Creating /root/.helm/cache/archive 
Creating /root/.helm/repository/repositories.yaml 
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com 
Adding local repo with URL: http://127.0.0.1:8879/charts 
$HELM_HOME has been configured at /root/.helm.
Not installing Tiller due to 'client-only' flag having been set
"gitlab" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):
	Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused
...Successfully got an update from the "gitlab" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
Saving 1 charts
Downloading postgresql from repo https://kubernetes-charts.storage.googleapis.com/
Deleting outdated charts
Hang tight while we grab the latest from your chart repositories...
...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):
	Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused
...Successfully got an update from the "gitlab" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
Saving 1 charts
Downloading postgresql from repo https://kubernetes-charts.storage.googleapis.com/
Deleting outdated charts
$ auto-deploy ensure_namespace
NAME                              STATUS   AGE
monitor-sandbox-4422333-staging   Active   85d
$ auto-deploy initialize_tiller
Checking Tiller...
Tiller is listening on localhost:44134
Client: &version.Version{SemVer:"v2.16.7", GitCommit:"5f2584fd3d35552c4af26036f0c464191287986b", GitTreeState:"clean"}
[debug] SERVER: "localhost:44134"

Kubernetes: &version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.10-gke.36", GitCommit:"34a615f32e9a0c9e97cdb9f749adb392758349a6", GitTreeState:"clean", BuildDate:"2020-04-06T16:33:17Z", GoVersion:"go1.12.12b4", Compiler:"gc", Platform:"linux/amd64"}
Server: &version.Version{SemVer:"v2.16.7", GitCommit:"5f2584fd3d35552c4af26036f0c464191287986b", GitTreeState:"clean"}

$ auto-deploy create_secret
Create secret...
$ auto-deploy deploy
Detected an existing PostgreSQL database installed on the
deprecated channel 1, but the current channel is set to 2. The default
channel changed to 2 in of GitLab 13.0.

- To continue using the channel 1 PostgreSQL database, set
  AUTO_DEVOPS_POSTGRES_CHANNEL to 1 and redeploy

- OR, to proceed with deleting the channel 1 PostgreSQL database
  and install a fresh channel 2 database, set AUTO_DEVOPS_POSTGRES_DELETE_V1
  to a non-empty value and redeploy.

  WARNING: This will PERMANENTLY DELETE the existing channel 1 database.

  For details on backing up your database and upgrading channels, see
  https://docs.gitlab.com/ee/topics/autodevops/upgrading_postgresql.html

NOTE: This detection is based on the postgresql.enabled Helm value for your
release, which is controlled by the POSTGRES_ENABLED CI variable. If you are
not using the in-cluster PostgreSQL database at all, you can also set the CI
variable POSTGRES_ENABLED to false.

WARNING: Setting POSTGRES_ENABLED to false will permanently delete any existing
channel 1 database.
section_end:1594396031:step_script
ERROR: Job failed: exit code 1