ansible-playbock fails sometime

In the context of https://gitlab.com/gitlab-org/quality/team-tasks/issues/66, I'm trying to understand the packaging process. My findings are written in https://gitlab.com/gitlab-org/quality/team-tasks/issues/66#note_122865000.

That said, I noticed that the ansible-playbook job failed for the last 11.9.0-rc6-ee tagged package: https://gitlab.com/gitlab-org/distribution/gitlab-provisioner/-/jobs/177102051

TASK [app : Apply migrations] **************************************************
fatal: [ci-pipeline-51696785-application-0]: FAILED! => {"changed": true, "cmd": ["/opt/gitlab/bin/gitlab-rake", "gitlab:db:configure"], "delta": "0:00:37.123555", "end": "2019-03-13 18:17:30.904059", "msg": "non-zero return code", "rc": 1, "start": "2019-03-13 18:16:53.780504", "stderr": "rake aborted!\nPG::ConnectionBad: could not connect to server: Connection refused\n\tIs the server running on host \"127.0.0.1\" and accepting\n\tTCP/IP connections on port 6432?\n/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/db.rake:52:in `block (3 levels) in <top (required)>'\n/opt/gitlab/embedded/bin/bundle:23:in `load'\n/opt/gitlab/embedded/bin/bundle:23:in `<main>'\nTasks: TOP => gitlab:db:configure\n(See full trace by running task with --trace)", "stderr_lines": ["rake aborted!", "PG::ConnectionBad: could not connect to server: Connection refused", "\tIs the server running on host \"127.0.0.1\" and accepting", "\tTCP/IP connections on port 6432?", "/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/db.rake:52:in `block (3 levels) in <top (required)>'", "/opt/gitlab/embedded/bin/bundle:23:in `load'", "/opt/gitlab/embedded/bin/bundle:23:in `<main>'", "Tasks: TOP => gitlab:db:configure", "(See full trace by running task with --trace)"], "stdout": "", "stdout_lines": []}
	to retry, use: --limit @/builds/gitlab-org/distribution/gitlab-provisioner/ansible/pg_ha.retry

PLAY RECAP *********************************************************************
ci-pipeline-51696785-application-0 : ok=11   changed=4    unreachable=0    failed=1   
ci-pipeline-51696785-consul-0 : ok=9    changed=2    unreachable=0    failed=0   
ci-pipeline-51696785-consul-1 : ok=9    changed=2    unreachable=0    failed=0   
ci-pipeline-51696785-consul-2 : ok=9    changed=2    unreachable=0    failed=0   
ci-pipeline-51696785-database-0 : ok=13   changed=5    unreachable=0    failed=0   
ci-pipeline-51696785-database-1 : ok=11   changed=3    unreachable=0    failed=1   
ci-pipeline-51696785-database-2 : ok=11   changed=7    unreachable=0    failed=0   

ERROR: Job failed: exit code 2

The triggering omnibus-gitlab pipeline can be found at https://dev.gitlab.org/gitlab/omnibus-gitlab/pipelines/106960.

@ibaum Do you have any idea about his error?