Timeout in jobs possibly due to networking issue
Summary
Opening this issue to log instances of jobs timing out due to networking issues.
Customer A reported in Feb 2023 on jobs timing out for instances due to networking issues, such as download an archive (30MB) from Nodejs, trying to read the deployment status on GCP. These are outside their control. #g_runner_saas confirmed this is the case. Ticket (internal only): https://gitlab.zendesk.com/agent/tickets/378392.
Customer A reached out to us again in May 2023 on 33 jobs timing out after 20 minutes. Checking with #g_runner_saas if the timeouts are also related to networking. Ticket (internal only): https://gitlab.zendesk.com/agent/tickets/411670.
Steps to reproduce
Example Project
What is the current bug behavior?
What is the expected correct behavior?
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)