127.0.0.1:3000/-/readiness returns failed status

Overview

During this investigation (#1836 (comment 1406544797)), it was discovered that the http://127.0.0.1:3000/-/readiness consistently returns a failed status in GDK Gitpod Docker image. Later, it was found out that the same issue occurs in the local GDK as well, even though GitLab starts up successfully.

{
  "status": "failed",
  "master_check": [
    {
      "status": "failed",
      "message": "unexpected Master check result: false"
    }
  ]
}

The goal of this issue is to investigate and address the root cause of this problem.

Impacted categories

The following categories relate to this issue:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Steps to replicate (optional)

Proposal (optional)

Environment (optional)

• Operating system name: <!-- output of `uname -a` command -->
• Architecture: <!-- output of `arch` command -->
• The contents of your gdk.yml (if any)
• Ruby version: <!-- output of `ruby --version` command -->
• GDK version: <!-- output of `git rev-parse --short HEAD` command -->