Upgrading to 1.16.2 does not work #8612

Closed
opened 2025-11-02 08:12:26 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @kolaente on GitHub (Feb 25, 2022).

Gitea Version

1.16.2

Git Version

No response

Operating System

Docker

How are you running Gitea?

Using the official docker image gitea/gitea:1.16.2.

Database

MySQL

Can you reproduce the bug on the Gitea demo site?

No - Not relevant I guess?

Log Gist

https://gist.github.com/kolaente/275fe9b431bc85feff1e42cc1a1fb40f

Description

Upgrading from gitea 1.16.1 to 1.16.2 fails with

[E] ORM engine initialization attempt #9/10 failed. Error: migrate: migration[210]: v208 was completely broken - remigrate failed: unable to (re)insert webauthn_credential[6]. Error: Error 1062: Duplicate entry 'fido-1' for key 'UQE_webauthn_credential_s'

Removing the key from the database would probably fix it, but I guess it would also require me to re-add the key to my account?

Screenshots

No response

Originally created by @kolaente on GitHub (Feb 25, 2022). ### Gitea Version 1.16.2 ### Git Version _No response_ ### Operating System Docker ### How are you running Gitea? Using the official docker image `gitea/gitea:1.16.2`. ### Database MySQL ### Can you reproduce the bug on the Gitea demo site? No - Not relevant I guess? ### Log Gist https://gist.github.com/kolaente/275fe9b431bc85feff1e42cc1a1fb40f ### Description Upgrading from gitea 1.16.1 to 1.16.2 fails with ``` [E] ORM engine initialization attempt #9/10 failed. Error: migrate: migration[210]: v208 was completely broken - remigrate failed: unable to (re)insert webauthn_credential[6]. Error: Error 1062: Duplicate entry 'fido-1' for key 'UQE_webauthn_credential_s' ``` Removing the key from the database would probably fix it, but I guess it would also require me to re-add the key to my account? ### Screenshots _No response_
Author
Owner

@kolaente commented on GitHub (Feb 25, 2022):

Can confirm removing the key entry it complains about lets me upgrade properly.

@kolaente commented on GitHub (Feb 25, 2022): Can confirm removing the key entry it complains about lets me upgrade properly.
Author
Owner

@kolaente commented on GitHub (Feb 25, 2022):

Maybe duplicate of #18881

@kolaente commented on GitHub (Feb 25, 2022): Maybe duplicate of #18881
Author
Owner

@mjanssens commented on GitHub (Mar 3, 2022):

Just to confirm. 1.16.2 would not start, failed with this issue report.
Waited for 1.16.3, installed it and it's working now.
I did not do any manual modifications on the DB (Postgresql) in between these versions.
So thanks.

@mjanssens commented on GitHub (Mar 3, 2022): Just to confirm. 1.16.2 would not start, failed with this issue report. Waited for 1.16.3, installed it and it's working now. I did not do any manual modifications on the DB (Postgresql) in between these versions. So thanks.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#8612