2020-10-16: Failed to open TCP connection to gitlab-registry:5000 (Connection refused - connect(2) for "gitlab-registry" port 5000)

Summary

2020-10-16: Failed to open TCP connection to gitlab-registry:5000 (Connection refused - connect(2) for "gitlab-registry" port 5000)

Creating this incident in order to note and track around 16 distinct occurrences of the error: Failed to open TCP connection to gitlab-registry:5000 (Connection refused - connect(2) for "gitlab-registry" port 5000)

I suspect that this is a hiccup in Google's networking, because it apparently no longer occurs, and subsequent job retries were successful.

There were no production alerts about these errors.

Timeline

All times UTC.

2020-10-16


Click to expand or collapse the Incident Review section.

Incident Review

Summary

  1. Service(s) affected:
  2. Team attribution:
  3. Minutes downtime or degradation:

Metrics

Customer Impact

  1. Who was impacted by this incident? (i.e. external customers, internal customers)
  2. What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
  3. How many customers were affected?
  4. If a precise customer impact number is unknown, what is the estimated potential impact?

Incident Response Analysis

  1. How was the event detected?
  2. How could detection time be improved?
  3. How did we reach the point where we knew how to mitigate the impact?
  4. How could time to mitigation be improved?

Post Incident Analysis

  1. How was the root cause diagnosed?
  2. How could time to diagnosis be improved?
  3. Do we have an existing backlog item that would've prevented or greatly reduced the impact of this incident?
  4. Was this incident triggered by a change (deployment of code or change to infrastructure. If yes, have you linked the issue which represents the change?)?

5 Whys

Lessons Learned

Corrective Actions

Guidelines

Edited by Nels Nelson