Harbor upgrading from 2.8 to 2.10 database migration fails

[Mooghens]

I am stuck here in a harbor upgrade going from 2.8 to 2.10

Normally we have been doing this succesfully for multiple other projects, however on this particular one, it is causing issues i cannot for the life of me tell why. When trying to run ./install.sh i get the following

[/common/dao/pgsql.go:135]: Upgrading schema for pgsql ...

2025-09-04T10:54:34Z [ERROR] [/common/dao/pgsql.go:140]: Failed to upgrade schema, error: "Dirty database version 120. Fix and force version."

Now normally, the supposed fix for this which has been working both for other projects has been to manually unset the dirty flag in the postgres db as mentioned in #19469
However when trying to do this in this particular case, install.sh proceeds normally afterwards, however when i go to the WEB GUI and attempt to run a vulnerabillity scan, the core log throws the following SQL error

2025-09-04T11:01:46Z [ERROR] [/lib/http/error.go:57]: {"errors":[{"code":"UNKNOWN","message":"unknown: ERROR: column s.critical_cnt does not exist (SQLSTATE 42703)"}]}
Any help in brainstorming this would be deeply appreciated

[MinerYang]

Hi @Mooghens ,

Generally, we support N-2 upgrade path.
You may follow this WIKI page and try to fix the dirty database issue manually.
https://github.com/goharbor/harbor/wiki/Harbor-FAQs#upgrade

Best,
Miner