staging
Failed Started
by
@syasonik-admin
Sarah Yasonik
The deployment of this job to staging did not succeed.
This job is archived. Only the complete pipeline can be retried.
1Running with gitlab-runner 13.1.0 (6214287e)2 on docker-auto-scale fa6cab464Using Docker executor with image registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.17.0 ...5Pulling docker image registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.17.0 ...6Using docker image sha256:f3e93bdc0fc2992fbc7a273e897f5f2f1d37c1a4e64cc3e5b53c5c9a1e73dc73 for registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.17.0 ...8Running on runner-fa6cab46-project-4422333-concurrent-0 via runner-fa6cab46-stg-srm-1594395950-1a52feda...10$ eval "$CI_PRE_CLONE_SCRIPT"11Fetching changes with git depth set to 50...12Initialized empty Git repository in /builds/gitlab-org/monitor/monitor-sandbox/.git/13Created fresh repository.14Checking out 58558c76 as master...15Skipping Git submodules setup17Downloading artifacts for dast_environment_deploy (37557109)...18Downloading artifacts from coordinator... ok id=37557109 responseStatus=200 OK token=uKdfpr4L20$ auto-deploy check_kube_domain21$ auto-deploy download_chart22Creating /root/.helm 23Creating /root/.helm/repository 24Creating /root/.helm/repository/cache 25Creating /root/.helm/repository/local 26Creating /root/.helm/plugins 27Creating /root/.helm/starters 28Creating /root/.helm/cache/archive 29Creating /root/.helm/repository/repositories.yaml 30Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com 31Adding local repo with URL: http://127.0.0.1:8879/charts 32$HELM_HOME has been configured at /root/.helm.33Not installing Tiller due to 'client-only' flag having been set34"gitlab" has been added to your repositories35Hang tight while we grab the latest from your chart repositories...36...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):37 Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused38...Successfully got an update from the "gitlab" chart repository39...Successfully got an update from the "stable" chart repository40Update Complete.41Saving 1 charts42Downloading postgresql from repo https://kubernetes-charts.storage.googleapis.com/43Deleting outdated charts44Hang tight while we grab the latest from your chart repositories...45...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):46 Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused47...Successfully got an update from the "gitlab" chart repository48...Successfully got an update from the "stable" chart repository49Update Complete.50Saving 1 charts51Downloading postgresql from repo https://kubernetes-charts.storage.googleapis.com/52Deleting outdated charts53$ auto-deploy ensure_namespace54NAME STATUS AGE55monitor-sandbox-4422333-staging Active 85d56$ auto-deploy initialize_tiller57Checking Tiller...58Tiller is listening on localhost:4413459Client: &version.Version{SemVer:"v2.16.7", GitCommit:"5f2584fd3d35552c4af26036f0c464191287986b", GitTreeState:"clean"}60[debug] SERVER: "localhost:44134"61Kubernetes: &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"}62Server: &version.Version{SemVer:"v2.16.7", GitCommit:"5f2584fd3d35552c4af26036f0c464191287986b", GitTreeState:"clean"}63$ auto-deploy create_secret64Create secret...65$ auto-deploy deploy66Detected an existing PostgreSQL database installed on the67deprecated channel 1, but the current channel is set to 2. The default68channel changed to 2 in of GitLab 13.0.69- To continue using the channel 1 PostgreSQL database, set70 AUTO_DEVOPS_POSTGRES_CHANNEL to 1 and redeploy71- OR, to proceed with deleting the channel 1 PostgreSQL database72 and install a fresh channel 2 database, set AUTO_DEVOPS_POSTGRES_DELETE_V173 to a non-empty value and redeploy.74 WARNING: This will PERMANENTLY DELETE the existing channel 1 database.75 For details on backing up your database and upgrading channels, see77NOTE: This detection is based on the postgresql.enabled Helm value for your78release, which is controlled by the POSTGRES_ENABLED CI variable. If you are79not using the in-cluster PostgreSQL database at all, you can also set the CI80variable POSTGRES_ENABLED to false.81WARNING: Setting POSTGRES_ENABLED to false will permanently delete any existing82channel 1 database.83ERROR: Job failed: exit code 1