2024-11-25: Incorrect banner warning for missing LFS files

Customer Impact

Right now the feature flag is disabled but we unfortunately merged an MR to remove the feature flag at gitlab-org/gitlab!173318 (merged) . We are now reverting that in gitlab-org/gitlab!173781 (merged) but we don't want to deploy the MR which removes the feature flag.

The customer impact is that many customers may see a big banner on their projects which says that LFS is misconfigured for their project. This will cause confusion as the banner is usually wrong. There is a risk that we get an influx of customer support requests and frustrated users if we deploy this. We are not yet sure how many customers this will impact but we know internally that many of our projects were impacted by this.

There are some examples in Slack from the brief time where the feature flag was enabled:

Current Status

More information will be added as we investigate the issue. For customers believed to be affected by this incident, please subscribe to this issue or monitor our status page for further updates.

📚 References and helpful links

Recent Events (available internally only):

Feature Flag Log - Chatops to toggle Feature Flags Documentation
Infrastructure Configurations
GCP Events (e.g. host failure)

Deployment Guidance

Use the following links to create related issues to this incident if additional work needs to be completed after it is resolved:

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 our 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.

Security Note: If anything abnormal is found during the course of your investigation, please do not hesitate to contact security.

Edited Nov 25, 2024 by Dylan Griffith (ex GitLab)