2021-09-14 ops.gitlab.net certificate inconsistencies

Current Status

AFter https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/14111 we're seeing intermittent results, even from the same endpoint (e.g. my laptop). Sometimes we get the old (soon to expire) certificate, sometimes we get the new one, but problematically the new cert only returns two certs the chain:

  1. ops.gitlab.net
  2. Subject: C = US, O = "Cloudflare, Inc.", CN = Cloudflare Inc ECC CA-3, Issuer: C = IE, O = Baltimore, OU = CyberTrust, CN = Baltimore CyberTrust Root

It doesn't include the actual root in the chain, which is believed to be leading to failures like:

fatal: unable to access 'https://ops.gitlab.net/gitlab-org/release/tools.git/': SSL certificate problem: unable to get local issuer certificate

(https://ops.gitlab.net/gitlab-org/release/tools/-/jobs/4861093) from git and other CLI tools, interrupting pipelines intermittently (retries are known to work somtimes, but that's not a solution).

Counter point is that on my laptop doing a CLI git clone over https is known to work, even if the cert returned is the new one. It's possible that our CI images need an updated cert store or something similar

Timeline

View recent production deployment and configuration events / gcp events (internal only)

All times UTC.

2021-09-14

  • 01:43 - @cmiskell declares incident in Slack.

Corrective Actions

Corrective actions should be put here as soon as an incident is mitigated, ensure that all corrective actions mentioned in the notes below are included.

  • ...

Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in out handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.


Click to expand or collapse the Incident Review section.

Incident Review
  • Ensure that the exec summary is completed at the top of the incident issue, the timeline is updated and relevant graphs are included in the summary
  • If there are any corrective action items mentioned in the notes on the incident, ensure they are listed in the "Corrective Action" section
  • Fill out relevant sections below or link to the meeting review notes that cover these topics

Customer Impact

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

What were the root causes?

  • ...

Incident Response Analysis

  1. How was the incident detected?
    1. ...
  2. How could detection time be improved?
    1. ...
  3. How was the root cause diagnosed?
    1. ...
  4. How could time to diagnosis be improved?
    1. ...
  5. How did we reach the point where we knew how to mitigate the impact?
    1. ...
  6. How could time to mitigation be improved?
    1. ...
  7. What went well?
    1. ...

Post Incident Analysis

  1. Did we have other events in the past with the same root cause?
    1. ...
  2. Do we have existing backlog items that would've prevented or greatly reduced the impact of this incident?
    1. ...
  3. Was this incident triggered by a change (deployment of code or change to infrastructure)? If yes, link the issue.
    1. ...

Lessons Learned

  • ...

Guidelines

Resources

  1. If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)
Edited by Craig Miskell