Project removing issue since 14.6.0-ee

First, happy new year to gitlab developpers & users (even if it start badly for me :disappointed: )

I was using a test project in gitlab-ee-14.6.0-ee.0.el8.x86_64 and decide to delete it to restart with a clean final project (same name/url).

However I was unable to remove this project. All seams to work but the project was still there. Only the reposit was deleted.

So gitlab web interface allows me to create an empty new repository in the project and push the fresh source tree and this works, belonging to the same group of users as previously. But now each time I connect to the web interface I get a message at the top of the page: “This project was scheduled for deletion, but failed with the following message: no repository for such path”


  • is my situation stable (or how to go to a stable state)
  • if yes, how to remove this message ?

Thanks for your help

I’ve restarted from a backup (my gitlab instance is in a VM) and utpdate to gitlab-ee-14.6.0-ee.0.el8.x86_64 from gitlab-ee-14.2.4 with some error messages but all seams to work and Yum is happy. Reboot to be confident, then:

  1. Login “patrick”, create a project and push something.
  2. Login “root” select the project (from “explore projects”), then “settings”->“General”->“Advanced”->“Delete project”. The project is removed.
  3. Login “patrick” again the project is still there with the warning “No repository” (no more files)
  4. Then I can choose to initialize and if I click I get “error 500 Whoops, something went wrong on our end.”

This works fine with gitlab-ee-14.2.4

Same problem this morning:
Update from a working gitlab-ee-14.5.2 to the just published gitlab-ee-14.6.1.

No one else has this bad behavior ? Limited to Alma linux 8 (RedHat8) ?

Yes, same here, running the gitlab/gitlab-ce:latest container (tried both 14.6.0/14.6.1) (on Debian Bullseye)

I just had success by deleting the project using the API:


Before restoring the backup of my VM I try to downgrade to the previously working gitlab-ee-14.5.2, as if I was in production and after the failure of removing a project (Ok it notice my new version doesn’t work, rollback to previous version!).
I follow: Back up and restore GitLab | GitLab

But the rollback fails at the ultimate step:

# gitlab-rake gitlab:check SANITIZE=true
Checking GitLab subtasks ...

rake aborted!
ActiveRecord::StatementInvalid: PG::UndefinedTable: ERROR:  relation "geo_nodes" does not exist
LINE 8:  WHERE a.attrelid = '"geo_nodes"'::regclass
/opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/database/schema_cache_with_renamed_table.rb:25:in `columns'
/opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/database/schema_cache_with_renamed_table.rb:29:in `columns_hash'
/opt/gitlab/embedded/service/gitlab-rails/config/initializers/postgresql_cte.rb:100:in `build_arel'
/opt/gitlab/embedded/service/gitlab-rails/ee/lib/gitlab/geo.rb:55:in `block in enabled?'
/opt/gitlab/embedded/service/gitlab-rails/ee/lib/gitlab/geo.rb:119:in `block (2 levels) in cache_value'
/opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/json_cache.rb:51:in `fetch'
/opt/gitlab/embedded/service/gitlab-rails/ee/lib/gitlab/geo.rb:119:in `block in cache_value'
/opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/json_cache.rb:51:in `fetch'
/opt/gitlab/embedded/service/gitlab-rails/ee/lib/gitlab/geo.rb:118:in `cache_value'
/opt/gitlab/embedded/service/gitlab-rails/ee/lib/gitlab/geo.rb:55:in `enabled?'
/opt/gitlab/embedded/service/gitlab-rails/ee/lib/ee/system_check/rake_task/gitlab_task.rb:16:in `subtasks'
/opt/gitlab/embedded/service/gitlab-rails/lib/system_check/rake_task/gitlab_task.rb:16:in `manual_run_checks!'
/opt/gitlab/embedded/service/gitlab-rails/lib/system_check/rake_task/rake_task_helpers.rb:13:in `run!'
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/check.rake:6:in `block (2 levels) in <top (required)>'
/opt/gitlab/embedded/bin/bundle:23:in `load'
/opt/gitlab/embedded/bin/bundle:23:in `<main>'

Caused by:
PG::UndefinedTable: ERROR:  relation "geo_nodes" does not exist
LINE 8:  WHERE a.attrelid = '"geo_nodes"'::regclass

take a look at

Note: You should be able to delete project after you delete all pipelines inside (even empty or full pipelines).

We’re waiting for GitLab Staff to start watching this issue :frowning:

Hope this helps,
and have you all a good 2022 :slight_smile:

Thanks Zionio.
As I have to switch in production this small gitlab instance, I have restored my VM backup and just upgrade Gitlab to 14.5.2.
I’ll wait for the new gitlab-ee version tu upgrade.