Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate 1.13.7 to 1.14.1 failed, need help #15505

Closed
yusiwen opened this issue Apr 16, 2021 · 7 comments
Closed

Migrate 1.13.7 to 1.14.1 failed, need help #15505

yusiwen opened this issue Apr 16, 2021 · 7 comments
Labels
type/bug type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@yusiwen
Copy link

yusiwen commented Apr 16, 2021

The error output of gitea-1.14.1-linux-amd64 doctor --all is shown below:

[2] Check Database Version
 - [C] Error: migrate: Current database version 156 is not equal to the expected version 178. Please run "gitea [--config /path/to/app.ini] migrate" to update the database version during ensure up to date
ERROR
[3] Check consistency of database
 - [C] Model version on the database does not match the current Gitea version. Model consistency will not be checked until the database is upgraded
ERROR

The output of gitea-1.14.1-linux-amd64 migrate is shown below:

...
2021/04/16 15:26:55 ...ations/migrations.go:397:Migrate() [I] [SQL] ROLLBACK [] - 353.864µs
2021/04/16 15:26:55 cmd/migrate.go:38:runMigrate() [F] Failed to initialize ORM engine: migrate: do migrate: GetTagCommit: object does not exist [id: f1beee0c8b030aec9c2863ebf884f8eb88d9ed6c, rel_path: ]

It seems something in the database is missing, anyone can help? Thanks

@yusiwen
Copy link
Author

yusiwen commented Apr 16, 2021

BTW, the diagnostic result of gitea-1.13.7-linux-amd64 doctor --all is all green, no error found. 1.13.7 is my current running version.

@lunny lunny added the type/bug label Apr 16, 2021
@lunny lunny added this to the 1.14.2 milestone Apr 16, 2021
@zeripath
Copy link
Contributor

Hmm. It would be useful to know if using 1.14.0 first succeed. (This is an unusual step that I would not normally recommend.)

I need to know if what you're running on: Windows, Linux or something else and if you're using gogit.

There is a release which is referring to an object in your gitea-repositories that is not present - presumably because a tag has been deleted.

The solution is to make this migration a bit more tolerant and I will do that but you should try to find out what has happened.

@raucao
Copy link

raucao commented Apr 17, 2021

Same issue here, also with 1.14.0.

@zeripath
Copy link
Contributor

Should be fixed by #15519 & its backport #15527

@6543
Copy link
Member

6543 commented Apr 30, 2021

@yusiwen can you confirm that it is fixed by using https://dl.gitea.io/gitea/1.14/ binary?

@6543
Copy link
Member

6543 commented May 7, 2021

@raucao is it solved ☝️ ?

@6543 6543 added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label May 7, 2021
@6543 6543 removed this from the 1.14.2 milestone May 7, 2021
@zeripath
Copy link
Contributor

zeripath commented May 7, 2021

I'm going to close this as fixed. Please reopen if this is still an issue.

@zeripath zeripath closed this as completed May 7, 2021
@go-gitea go-gitea locked as resolved and limited conversation to collaborators May 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/bug type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

5 participants