"Gitaly, is not available at this time" message should be coupled to unhealthy output from "gitlab-rake gitlab:gitaly:check"
Release notes
Previously, it was possible that gitlab-rake gitlab:gitaly:check
output reported healthy
despite GitLab UI reporting Gitaly as unavailable. The cases in which this discrepancy was possible, were resolved.
Problem to solve
A customer reported a situation in which gitlab-rake gitlab:gitaly:check
output reported that all nodes were healthy, despite one "DoSing [its own Linux] process table" due to a custom Git hook spawning too many processes.
In the GitLab UI, this caused the "git server, Gitaly, is not available at this time" message to be shown.
Proposal
Align the conditionals for both outputs, so that there is no discrepancy between admin-level check
output and user-visible UI alerts.
Also, might we need to add more details to be checked beyond network latency and connectivity & the currently used health conditions for "Repository-specific primary nodes"?
Intended users
Feature Usage Metrics
Does this feature require an audit event?
No.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.