Service degradation when displaying Request's changes

There was a service degradation of our reference server.

After a deployment of on Tuesday, March 19, 10:36 UTC, accessing the changes on some Submit Requests showed this error to the users:

Not all Submit Requests were affected. Specifically, only those requests that had changes on files containing a slash symbol in its path (e.g: buildah-1.35.1.tar.xz/

Our production instance was back to normal operation at 13:05 UTC, so users were impacted by this during 2,5 hours.

We want to give you some insight into what happened and what we are doing to avoid similar problems in the future.


We were contacted by a user, from there, we saw that there were errors in our error collector since 10:36 UTC.

Root Cause

The root cause was a refactoring we introduced on the file viewing capabilities of OBS. That refactoring introduced the rejection of file names containing slashes. Not having a comprehensive test coverage prior to that refactoring made the detection of that flaw impossible.


We corrected the code to avoid linking to filenames with slashes and wrote a use case in our test suite to cover this.

Action Items


Lessons Learned

  • We were not aware the code before the refactoring was producing filenames with slashes, and happily accepting them.
  • Before refactoring anything, we need a comprehensive test coverage to ensure we are not introducing errors.

Timeline (All Time in UTC)

  • 2024-03-19 10:36 First appearance of the error in our error collector.
  • 2024-03-19 12:37 Some user detected an issue.
  • 2024-03-19 12:45 The incident was declared.
  • 2024-03-19 13:05 We monkey patched production to stop the issue from affecting the users.
  • 2024-03-19 13:05 The incident is resolved
  • 2024-03-20 12:51 The fix was merged.
  • 2024-03-20 16:40 The fix was deployed.