staging
Failed Started
by
@rpereira2
Reuben Pereira
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.2.0-rc2 (45f2b4ec)2 on docker-auto-scale fa6cab464Using Docker executor with image registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.17.2 ...5Pulling docker image registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.17.2 ...6Using docker image sha256:f781f08f0eb89174bc3c66176dea9a890d3db607b6c426bccaec80456360eae9 for registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.17.2 ...8Running on runner-fa6cab46-project-4422333-concurrent-0 via runner-fa6cab46-stg-srm-1596123481-01157cf7...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 ec43926f as master...15Skipping Git submodules setup17$ auto-deploy check_kube_domain18$ auto-deploy download_chart19Creating /root/.helm 20Creating /root/.helm/repository 21Creating /root/.helm/repository/cache 22Creating /root/.helm/repository/local 23Creating /root/.helm/plugins 24Creating /root/.helm/starters 25Creating /root/.helm/cache/archive 26Creating /root/.helm/repository/repositories.yaml 27Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com 28Adding local repo with URL: http://127.0.0.1:8879/charts 29$HELM_HOME has been configured at /root/.helm.30Not installing Tiller due to 'client-only' flag having been set31"gitlab" has been added to your repositories32Hang tight while we grab the latest from your chart repositories...33...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):34 Get "http://127.0.0.1:8879/charts/index.yaml": dial tcp 127.0.0.1:8879: connect: connection refused35...Successfully got an update from the "gitlab" chart repository36...Successfully got an update from the "stable" chart repository37Update Complete.38Saving 1 charts39Downloading postgresql from repo https://kubernetes-charts.storage.googleapis.com/40Deleting outdated charts41Hang tight while we grab the latest from your chart repositories...42...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):43 Get "http://127.0.0.1:8879/charts/index.yaml": dial tcp 127.0.0.1:8879: connect: connection refused44...Successfully got an update from the "gitlab" chart repository45...Successfully got an update from the "stable" chart repository46Update Complete.47Saving 1 charts48Downloading postgresql from repo https://kubernetes-charts.storage.googleapis.com/49Deleting outdated charts50$ auto-deploy ensure_namespace51NAME STATUS AGE52monitor-sandbox-4422333-staging Active 105d53$ auto-deploy initialize_tiller54Checking Tiller...55Tiller is listening on localhost:4413456Client: &version.Version{SemVer:"v2.16.9", GitCommit:"8ad7037828e5a0fca1009dabe290130da6368e39", GitTreeState:"clean"}57[debug] SERVER: "localhost:44134"58Kubernetes: &version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.10-gke.42", GitCommit:"42bef28c2031a74fc68840fce56834ff7ea08518", GitTreeState:"clean", BuildDate:"2020-06-02T16:07:00Z", GoVersion:"go1.12.12b4", Compiler:"gc", Platform:"linux/amd64"}59Server: &version.Version{SemVer:"v2.16.9", GitCommit:"8ad7037828e5a0fca1009dabe290130da6368e39", GitTreeState:"clean"}60$ auto-deploy create_secret61Create secret...62$ auto-deploy deploy63Detected an existing PostgreSQL database installed on the64deprecated channel 1, but the current channel is set to 2. The default65channel changed to 2 in of GitLab 13.0.66- To continue using the channel 1 PostgreSQL database, set67 AUTO_DEVOPS_POSTGRES_CHANNEL to 1 and redeploy68- OR, to proceed with deleting the channel 1 PostgreSQL database69 and install a fresh channel 2 database, set AUTO_DEVOPS_POSTGRES_DELETE_V170 to a non-empty value and redeploy.71 WARNING: This will PERMANENTLY DELETE the existing channel 1 database.72 For details on backing up your database and upgrading channels, see74NOTE: This detection is based on the postgresql.enabled Helm value for your75release, which is controlled by the POSTGRES_ENABLED CI variable. If you are76not using the in-cluster PostgreSQL database at all, you can also set the CI77variable POSTGRES_ENABLED to false.78WARNING: Setting POSTGRES_ENABLED to false will permanently delete any existing79channel 1 database.80ERROR: Job failed: exit code 1