# \[solved\] Gitea migration from 1.19.4 to 1.20.4 - failing

**URL:** <https://forum.gitea.com/t/solved-gitea-migration-from-1-19-4-to-1-20-4-failing/7874>\
**Category:** Install/Maintain/Configure\
**Created:** [September 21, 2023, 5:19am UTC](https://forum.gitea.com/t/solved-gitea-migration-from-1-19-4-to-1-20-4-failing/7874 "2023-09-21T05:19:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Baitanik](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/baitanik/32/3159_2.png) [@Baitanik](https://forum.gitea.com/u/Baitanik)\
**Post date:** [September 21, 2023, 5:19am UTC](https://forum.gitea.com/t/solved-gitea-migration-from-1-19-4-to-1-20-4-failing/7874/1 "2023-09-21T05:19:00Z")

</div>

We were using gitea 1.19.4 and trying to upgrade to 1.20.4.  
now with helm upgrade it the gitea pod is coming up properly.  
following in the app.ini  
APP\_NAME = CCM Hub  
WORK\_PATH = /data

[ui]  
DEFAULT\_THEME = company  
THEMES = company

[indexer]  
ISSUE\_INDEXER\_TYPE = db

[server]  
LFS\_JWT\_SECRET = xxxxxxxxxxxxxxxxxxxxxxx  
ROOT\_URL = [https://xxx.company.com/ccmgitea](https://xxx.company.com/ccmgitea)  
ENABLE\_PPROF = false  
SSH\_PORT = 22  
APP\_DATA\_PATH = /data  
SSH\_LISTEN\_PORT = 2222  
PROTOCOL = http  
HTTP\_PORT = 53000  
SSH\_DOMAIN = [xxx.xxx.mon.ngxp.com](http://xxx.xxx.mon.ngxp.com)  
DOMAIN = [xxx.xxx.mon.ngxp.com](http://xxx.xxx.mon.ngxp.com)

[database]  
NAME = giteadb  
DB\_TYPE = postgres  
HOST = xxxxxxxxxxx  
USER = xxxxxx  
PASSWD = xxxxxxxxx  
SCHEMA = gitea

[service]  
ENABLE\_REVERSE\_PROXY\_AUTHENTICATION = true  
DISABLE\_REGISTRATION = false  
ENABLE\_REVERSE\_PROXY\_AUTO\_REGISTRATION = true

[session]  
PROVIDER\_CONFIG =  
PROVIDER = memory

[repository]  
ROOT = /data/git/gitea-repositories

[security]  
INTERNAL\_TOKEN = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx  
SECRET\_KEY = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx  
INSTALL\_LOCK = true  
REVERSE\_PROXY\_AUTHENTICATION\_USER = HTTP\_IV\_USER

[queue]  
TYPE = dummy

[cache]  
ADAPTER = memory

[metrics]  
ENABLED = false

[oauth2]  
JWT\_SECRET = xxxxxxxxxxxxxxxx

==========  
Gitea pod is coming up with deployment. but the old repositories are not properly migrated.  
In gui, in home list of all old repositories are showing , but when we click on the repositories following page is coming .

 ![image](https://us1.discourse-cdn.com/flex020/uploads/gitea/original/2X/e/ec03ba8e7aa7549f6889eb5dc1cda6877273c52c.png)

Could you please help in migrating the repos.  
we are using helm for gitea deployment.  
new version::  
helm chart version 9.4.0  
gitea version 1.20.4

old version::  
helm chart : 8.3.0  
gitea version : 1.19.4

---

<div class="post-metadata">

**Author:** ![lunny](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/lunny/32/4701_2.png) [@lunny](https://forum.gitea.com/u/lunny)\
**Post date:** [September 21, 2023, 7:56am UTC](https://forum.gitea.com/t/solved-gitea-migration-from-1-19-4-to-1-20-4-failing/7874/2 "2023-09-21T07:56:16Z")

</div>

Could you provide some logs?

---

<div class="post-metadata">

**Author:** ![Baitanik](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/baitanik/32/3159_2.png) [@Baitanik](https://forum.gitea.com/u/Baitanik)\
**Post date:** [September 21, 2023, 11:12am UTC](https://forum.gitea.com/t/solved-gitea-migration-from-1-19-4-to-1-20-4-failing/7874/3 "2023-09-21T11:12:03Z")

</div>

Looks like the pvc key name has been changed…  
earlier it was **existingClaim**  
now it is **claimName** … that was causing the issue… we have separate pvc created and we mount that to gitea using existingClaim.

after updated the key in OR value yaml it worked… thanks

---

<div class="post-metadata">

**Author:** ![techknowlogick](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/techknowlogick/32/4706_2.png) [@techknowlogick](https://forum.gitea.com/u/techknowlogick)\
**Post date:** [September 25, 2023, 5:44am UTC](https://forum.gitea.com/t/solved-gitea-migration-from-1-19-4-to-1-20-4-failing/7874/4 "2023-09-25T05:44:40Z")

</div>

Closed on September 25, 2023, 5:44am UTC