go-gitea / gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
https://gitea.com
MIT License
45.15k stars 5.49k forks source link

Error: migrate: migration[276]: Add RemoteAddress to mirrors failed: get remote origin's address of MyORG/MyPRJ failed: exit status 128 - fatal: not a git repository (or any parent up to mount point /) #31556

Open hellorayza opened 4 months ago

hellorayza commented 4 months ago

Description

I was upgrading gitea from 1.20 to 1.21, and after recovering the pg database and gitea custom files, the following error was reported at boot.

I tried version 1.22 again with the same result.

Complete startup information: https://forum.gitea.com/t/1-20-1-21/9388

The organization/repository displayed in the error message is the mirror repository that I cloned from the Intranet.

I found someone with a similar problem in another place. https://codeberg.org/forgejo/forgejo/issues/1800

Gitea Version

v1.21.11&1.22

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.39.1

Operating System

synology-dsm-docker

How are you running Gitea?

from official image on docker hub

Database

PostgreSQL

lunny commented 4 months ago

A side question: why did you need to recovery when upgrading?

hellorayza commented 4 months ago

A side question: why did you need to recovery when upgrading?

Because I am using a new machine and the database version is different, pg has changed from 12 to 14.

have no problem changing to the same database(pg12) and gitea(1.20) version.

But I use pg12 and gitea1.21 The same problem occurred.

hellorayza commented 4 months ago

I went back to the original version and tried to find out when the incomplete repository in the error message was generated.

RepoAssignment Invalid repo /data/git/repositories/orgname/xx-projectname.git, exit status 128 - fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

I have removed it from the admin interface, it should not affect the upgrade, thank you!