[solved] Gitea migration from 1.19.4 to 1.20.4 - failing

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
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
DOMAIN = 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 .

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

Could you provide some logs?

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