Unable to delete project if description length is 500 characters or above

Summary

A project cannot be deleted if the Project's Description has 500 characters or above. When you try to delete the project, the UI shows the following flash messages:

  • This project is pending deletion, and will be deleted on {date}. Repository and other project resources are read-only.
  • Project could not be updated!

When viewing the project again in the UI, or via API, the project is not pending deletion at all.

The workaround is to delete the project's description before attempting to delete the project.

Steps to reproduce

This has been reproduced in SaaS and GitLab Omnibus 18.1

  1. Create a new project
  2. Add 500 characters (or more) to the Project's Description and save.
  3. Attempt to delete the project via UI.

Example Project

https://gitlab.com/tmike/test-deletion-description-499-chars

What is the current bug behavior?

Project is not deleted.

What is the expected correct behavior?

Project is deleted.

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)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by Michael Trainor