Owner can not clone,pull,push created repository

I had to delete database for existing gitlab project (migration failed)
Fresh data base settings migrated from 15*.
2fA works, email, work, pipeline runners looks ready, user and admin account also looks correct, ssh access yes key are working.

I’ve tried to create repository to push copy from local to remote but I am not able to push…

Problem to solve

Newly created repository (Private, Internal) can not be accessed even by owner in read/write manner.
Public repository can be accessed by remote only in read only mode.
Gitlab web editor can create files in repository which can be later pulled.

Steps to reproduce

Create repository private/internal/public repository.
Try to clone it and push commit to it.

I am a project owner how its possible to get this kind of messages ?
errors: remote: The project you were looking for could not be found or you don’t have permission to view it.
You are not allowed to upload code for this project.

I’ve check merge and push policies, default settings - no go.
Manually configured loose settings - no go.

Versions

16.11.1-1

Versions

System information
System:         Arch rolling
Current User:   gitlab
Using RVM:      no
Ruby Version:   3.0.6p216
Gem Version:    3.3.25
Bundler Version:2.5.4
Rake Version:   13.0.6
Redis Version:  7.2.4
Sidekiq Version:7.1.6
Go Version:     go1.22.2 linux/amd64

GitLab information
Version:        16.11.1
Revision:       3ad2f8c9e62
Directory:      /usr/share/webapps/gitlab
DB Adapter:     PostgreSQL
DB Version:     16.2
URL:            https://<hidden>
HTTP Clone URL: https://<hidden>/some-group/some-project.git
SSH Clone URL:  ssh://<hidden>/some-group/some-project.git
Using LDAP:     no
Using Omniauth: no

GitLab Shell
Version:        14.35.0
Repository storages:
- default:      unix:/run/gitlab/gitlab-gitaly.socket
GitLab Shell path:              /usr/share/webapps/gitlab-shell

Gitaly
- default Address:      unix:/run/gitlab/gitlab-gitaly.socket
- default Version:      16.11.1
- default Git Version:  2.45.0

Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 14.35.0 ? ... OK (14.35.0)
Running /usr/share/webapps/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes
Number of Sidekiq processes (cluster/worker) ... 0/1
  Try fixing it:
  sudo systemctl restart gitlab-sidekiq.service
  Please fix the error above and rerun the checks.

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Database config exists? ... yes
Tables are truncated? ... skipped
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Cable config exists? ... yes
Resque config exists? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Systemd unit files or init script exist? ... no
  Try fixing it:
  Install the Service
  For more information see:
  doc/install/installation.md in section "Install the Service"
  Please fix the error above and rerun the checks.
Systemd unit files or init script up-to-date? ... can't check because of previous errors
Projects have namespace: ...
<hidden> / A ... yes
<hidden> / B ... yes
<hidden> / C ... yes
Redis version >= 6.2.14? ... yes
Ruby version >= 3.0.6 ? ... yes (3.0.6)
Git user has default SSH configuration? ... yes
Active users: ... 2
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... yes

Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished

System information
System:         Arch rolling
Current User:   gitlab
Using RVM:      no
Ruby Version:   3.0.6p216
Gem Version:    3.3.25
Bundler Version:2.5.4
Rake Version:   13.0.6
Redis Version:  7.2.4
Sidekiq Version:7.1.6
Go Version:     go1.22.2 linux/amd64

GitLab information
Version:        16.11.1
Revision:       3ad2f8c9e62
Directory:      /usr/share/webapps/gitlab
DB Adapter:     PostgreSQL
DB Version:     16.2
URL:            https://<hidden>
HTTP Clone URL: https://<hidden>/some-group/some-project.git
SSH Clone URL:  ssh://<hidden>/some-group/some-project.git
Using LDAP:     no
Using Omniauth: no

GitLab Shell
Version:        14.35.0
Repository storages:
- default:      unix:/run/gitlab/gitlab-gitaly.socket
GitLab Shell path:              /usr/share/webapps/gitlab-shell

Gitaly
- default Address:      unix:/run/gitlab/gitlab-gitaly.socket
- default Version:      16.11.1
- default Git Version:  2.45.0


Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 14.35.0 ? ... OK (14.35.0)
Running /usr/share/webapps/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes (always had this own, CI/CD was working so I don't care)
Number of Sidekiq processes (cluster/worker) ... 0/1
  Try fixing it:
  sudo systemctl restart gitlab-sidekiq.service
  Please fix the error above and rerun the checks.

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Database config exists? ... yes
Tables are truncated? ... skipped
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Cable config exists? ... yes
Resque config exists? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Systemd unit files or init script exist? ... no
  Try fixing it:
  Install the Service
  For more information see:
  doc/install/installation.md in section "Install the Service"
  Please fix the error above and rerun the checks.
Systemd unit files or init script up-to-date? ... can't check because of previous errors
Projects have namespace: ...
<hidden> / A ... yes
<hidden> / B ... yes
<hidden> / C ... yes
Redis version >= 6.2.14? ... yes
Ruby version >= 3.0.6 ? ... yes (3.0.6)
Git user has default SSH configuration? ... yes
Active users: ... 2
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... yes

Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished

What error messages do you see in the GitLab logs when you try to clone or push to it?

gitlab-shell

{"command":"*receivepack.Command","correlation_id":"01HXWCJA9WPWSD200H67SF68QJ","env":{"GitProtocolVersion":"","IsSSHConnection":true,"OriginalCommand":"git-receive-pack '<hidden>'","RemoteAddr":"<hidden>","NamespacePath":""},"level":"info","msg":"gitlab-shell: main: executing command","time":"2024-05-14T20:26:40Z"}
{"correlation_id":"01HXWCJA9WPWSD200H67SF68QJ","duration_ms":20,"error":null,"level":"error","method":"POST","msg":"Internal API error","status":404,"time":"2024-05-14T20:26:40Z","url":"http://unix/api/v4/internal/allowed"}
{"correlation_id":"01HXWCJA9WPWSD200H67SF68QJ","error":"The project you were looking for could not be found or you don't have permission to view it.","level":"warning","msg":"gitlab-shell: main: command execution failed","time":"2024-05-14T20:26:40Z"}

gitlab:shell:setup cleared keys after this operation gitlab is cooperating as it should be.
It look like there was error in migration code…

issue can be marked as solved and closed

1 Like