Assistance requested to find out why the gitlab-qa user keeps being temporarily blocked
Details
- Point of contact for this request: @mlapierre
SRE Support Needed Support Request Details
We (Quality Department) have an ongoing issue where the gitlab-qa
user keeps getting temporarily blocked on gitlab.com and staging.gitlab.com. What we see is that tests all suddenly fail because API requests return status 403
with the message 403 Forbidden - Your account has been blocked.
And then it's fine 10-15 minutes later.
Briefly, it doesn't appear to be due to an application-level block (some details here and here). I wanted to find out if it's being blocked at some point in the infrastructure before the requests hit the web service. We have at least one Cloudflare bypass in place for QA tests but I don't know if that affects rate-limiting, nor if that's the only bypass.
More details in gitlab-org/gitlab#375166 (closed)
Would it be possible to find out why the gitlab-qa
user keeps getting blocked? Or at least rule out some sort of rate-limit or IP block?