upgrade to v2.3.0 with empty db

[strajansebastian]

Hello,

I was looking over upgrading a harbor v2.1.3 setup to the latest v2.3.2 but after I had a failed direct upgrade (with the database empty) I started doing some more granular upgrade tests with the following results:

v2.1.3 -> v2.1.4 (success) -> v2.2.0 (success) -> v2.2.1 (success) -> v2.2.2 (success) -> v2.2.3 (success) -> v2.3.0 (fail - epmty db) -> v2.3.1 (fail, db still empty)
The old db seems to be somehow hidden due to the upgrade from v9 to v13.

Has anyone experienced this issue during the postgresql upgrade?

I'm using ubuntu 20.04 as the host system if that helps.
I put below the harbor-core log from the upgrade from v2.2.3 to v2.3.0 and v2.3.1 in case it helps.

Sep 3 22:50:58 192.168.208.1 core[740]: Appending internal tls trust CA to ca-bundle ...
Sep 3 22:50:58 192.168.208.1 core[740]: find: /etc/harbor/ssl: No such file or directory
Sep 3 22:50:58 192.168.208.1 core[740]: Internal tls trust CA appending is Done.
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/controller/artifact/annotation/parser.go:71]: the annotation parser to parser artifact annotation version v1alpha1 registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.cncf.helm.config.v1+json registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.cnab.manifest.v1 registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.oci.image.index.v1+json registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.distribution.manifest.list.v2+json registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.distribution.manifest.v1+prettyjws registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.oci.image.config.v1+json registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.container.image.v1+json registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/native/adapter.go:36]: the factory for adapter docker-registry registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/harbor/adaper.go:31]: the factory for adapter harbor registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/dockerhub/adapter.go:25]: Factory for adapter docker-hub registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/huawei/huawei_adapter.go:27]: the factory of Huawei adapter was registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/googlegcr/adapter.go:35]: the factory for adapter google-gcr registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/awsecr/adapter.go:42]: the factory for adapter aws-ecr registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/azurecr/adapter.go:15]: Factory for adapter azure-acr registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/aliacr/adapter.go:31]: the factory for adapter ali-acr registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/jfrog/adapter.go:47]: the factory of jfrog artifactory adapter was registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/quay/adapter.go:55]: the factory of Quay adapter was registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/helmhub/adapter.go:30]: the factory for adapter helm-hub registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/gitlab/adapter.go:17]: the factory for adapter gitlab registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/dtr/adapter.go:22]: the factory of dtr adapter was registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/artifacthub/adapter.go:30]: the factory for adapter artifact-hub registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/tencentcr/adapter.go:42]: the factory for adapter tencent-tcr registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/replication/adapter/githubcr/adapter.go:29]: the factory for adapter github-ghcr registered
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/core/controllers/base.go:299]: Config path: /etc/core/app.conf
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/core/main.go:164]: initializing cache ...
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/core/main.go:171]: initializing configurations...
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/core/config/config.go:77]: key path: /etc/core/key
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/core/config/config.go:57]: init secret store
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/core/main.go:173]: configurations initialization completed
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/common/dao/base.go:65]: Registering database: type-PostgreSQL host-postgresql port-5432 database-registry sslmode-"disable"
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/common/dao/base.go:70]: Register database completed
Sep 3 22:50:58 192.168.208.1 core[740]: 2021-09-03T22:50:58Z [INFO] [/common/dao/pgsql.go:127]: Upgrading schema for pgsql ...
Sep 3 22:50:59 192.168.208.1 core[740]: 2021-09-03T22:50:59Z [INFO] [/vendor/github.com/golang-migrate/migrate/v4/migrate.go:765]: 53/u 2.2.3_schema (175.760471ms)
Sep 3 22:50:59 192.168.208.1 core[740]: 2021-09-03T22:50:59Z [INFO] [/migration/migration.go:58]: Abstracting artifact data to DB...
Sep 3 22:50:59 192.168.208.1 core[740]: 2021-09-03T22:50:59Z [INFO] [/migration/migration.go:67]: No need to abstract artifact data. Skip
Sep 3 22:50:59 192.168.208.1 core[740]: 2021-09-03T22:50:59Z [INFO] [/common/config/encrypt/encrypt.go:60]: the path of key used by key provider: /etc/core/key
Sep 3 22:50:59 192.168.208.1 core[740]: 2021-09-03T22:50:59Z [INFO] [/core/main.go:85]: User id: 1 already has its encrypted password.
Sep 3 22:50:59 192.168.208.1 core[740]: 2021-09-03T22:50:59Z [INFO] [/chartserver/cache.go:185]: Enable redis cache for chart caching
Sep 3 22:50:59 192.168.208.1 core[740]: 2021-09-03T22:50:59Z [INFO] [/chartserver/reverse_proxy.go:60]: New chart server traffic proxy with middlewares
Sep 3 22:50:59 192.168.208.1 core[740]: 2021-09-03T22:50:59Z [INFO] [/core/api/chart_repository.go:618]: API controller for chart repository server is successfully initialized
Sep 3 22:50:59 192.168.208.1 core[740]: 2021-09-03T22:50:59Z [INFO] [/core/main.go:257]: Removing Trivy scanner
Sep 3 22:50:59 192.168.208.1 core[740]: 2021-09-03T22:50:59Z [INFO] [/core/main.go:216]: initializing notification...
Sep 3 22:50:59 192.168.208.1 core[740]: 2021-09-03T22:50:59Z [INFO] [/pkg/notification/notification.go:47]: notification initialization completed
Sep 3 22:50:59 192.168.208.1 core[740]: 2021-09-03T22:50:59Z [INFO] [/core/main.go:235]: Version: v2.2.3, Git commit: 74ecf35
Sep 3 22:50:59 192.168.208.1 core[740]: 2021/09/03 22:50:59.429 #33[1;34m[I]#33[0m [asm_amd64.s:1374] http server Running on http://:8080
Sep 3 22:56:13 192.168.240.1 core[740]: Appending internal tls trust CA to ca-bundle ...
Sep 3 22:56:13 192.168.240.1 core[740]: find: '/etc/harbor/ssl': No such file or directory
Sep 3 22:56:13 192.168.240.1 core[740]: Internal tls trust CA appending is Done.
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/controller/artifact/annotation/parser.go:71]: the annotation parser to parser artifact annotation version v1alpha1 registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.cncf.helm.config.v1+json registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.cnab.manifest.v1 registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.oci.image.index.v1+json registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.distribution.manifest.list.v2+json registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.distribution.manifest.v1+prettyjws registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.oci.image.config.v1+json registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.container.image.v1+json registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/native/adapter.go:36]: the factory for adapter docker-registry registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/harbor/adaper.go:31]: the factory for adapter harbor registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/dockerhub/adapter.go:25]: Factory for adapter docker-hub registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/huawei/huawei_adapter.go:42]: the factory of Huawei adapter was registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/googlegcr/adapter.go:35]: the factory for adapter google-gcr registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/awsecr/adapter.go:43]: the factory for adapter aws-ecr registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/azurecr/adapter.go:15]: Factory for adapter azure-acr registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/aliacr/adapter.go:31]: the factory for adapter ali-acr registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/jfrog/adapter.go:47]: the factory of jfrog artifactory adapter was registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/quay/adapter.go:55]: the factory of Quay adapter was registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/helmhub/adapter.go:30]: the factory for adapter helm-hub registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/gitlab/adapter.go:17]: the factory for adapter gitlab registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/dtr/adapter.go:22]: the factory of dtr adapter was registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/artifacthub/adapter.go:30]: the factory for adapter artifact-hub registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/tencentcr/adapter.go:42]: the factory for adapter tencent-tcr registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/pkg/reg/adapter/githubcr/adapter.go:29]: the factory for adapter github-ghcr registered
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/core/controllers/base.go:157]: Config path: /etc/core/app.conf
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/core/main.go:162]: initializing cache ...
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/core/main.go:169]: initializing configurations...
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/lib/config/systemconfig.go:197]: key path: /etc/core/key
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/lib/config/config.go:98]: init secret store
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/core/main.go:171]: configurations initialization completed
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/common/dao/base.go:65]: Registering database: type-PostgreSQL host-postgresql port-5432 database-registry sslmode-"disable"
Sep 3 22:56:13 192.168.240.1 core[740]: 2021-09-03T22:56:13Z [INFO] [/common/dao/base.go:70]: Register database completed
Sep 3 22:56:14 192.168.240.1 core[740]: 2021-09-03T22:56:14Z [INFO] [/common/dao/pgsql.go:127]: Upgrading schema for pgsql ...
Sep 3 22:56:14 192.168.240.1 core[740]: 2021-09-03T22:56:14Z [INFO] [/common/dao/pgsql.go:130]: No change in schema, skip.
Sep 3 22:56:14 192.168.240.1 core[740]: 2021-09-03T22:56:14Z [INFO] [/migration/migration.go:58]: Abstracting artifact data to DB...
Sep 3 22:56:14 192.168.240.1 core[740]: 2021-09-03T22:56:14Z [INFO] [/migration/migration.go:67]: No need to abstract artifact data. Skip
Sep 3 22:56:14 192.168.240.1 core[740]: 2021-09-03T22:56:14Z [INFO] [/core/main.go:83]: User id: 1 already has its encrypted password.
Sep 3 22:56:14 192.168.240.1 core[740]: 2021-09-03T22:56:14Z [INFO] [/chartserver/cache.go:185]: Enable redis cache for chart caching
Sep 3 22:56:14 192.168.240.1 core[740]: 2021-09-03T22:56:14Z [INFO] [/chartserver/reverse_proxy.go:60]: New chart server traffic proxy with middlewares
Sep 3 22:56:14 192.168.240.1 core[740]: 2021-09-03T22:56:14Z [INFO] [/core/api/chart_repository.go:621]: API controller for chart repository server is successfully initialized
Sep 3 22:56:14 192.168.240.1 core[740]: 2021-09-03T22:56:14Z [INFO] [/core/main.go:258]: Removing Trivy scanner
Sep 3 22:56:14 192.168.240.1 core[740]: 2021-09-03T22:56:14Z [INFO] [/core/main.go:217]: initializing notification...
Sep 3 22:56:14 192.168.240.1 core[740]: 2021-09-03T22:56:14Z [INFO] [/pkg/notification/notification.go:44]: notification initialization completed
Sep 3 22:56:14 192.168.240.1 core[740]: 2021-09-03T22:56:14Z [INFO] [/core/main.go:236]: Version: v2.3.0, Git commit: 047b122
Sep 3 22:56:14 192.168.240.1 core[740]: 2021/09/03 22:56:14.494 #33[1;34m[I]#33[0m [asm_amd64.s:1374] http server Running on http://:8080
Sep 3 22:58:43 192.168.240.1 core[740]: 2021-09-03T22:58:43Z [INFO] [/controller/registry/controller.go:221]: Start regular health check for registries with interval 5m0s
Sep 3 23:06:31 172.19.0.1 core[740]: Appending internal tls trust CA to ca-bundle ...
Sep 3 23:06:31 172.19.0.1 core[740]: find: '/etc/harbor/ssl': No such file or directory
Sep 3 23:06:31 172.19.0.1 core[740]: Internal tls trust CA appending is Done.
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/controller/artifact/annotation/parser.go:71]: the annotation parser to parser artifact annotation version v1alpha1 registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.cncf.helm.config.v1+json registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.cnab.manifest.v1 registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.oci.image.index.v1+json registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.distribution.manifest.list.v2+json registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.distribution.manifest.v1+prettyjws registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.oci.image.config.v1+json registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.container.image.v1+json registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/native/adapter.go:36]: the factory for adapter docker-registry registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/harbor/adaper.go:31]: the factory for adapter harbor registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/dockerhub/adapter.go:25]: Factory for adapter docker-hub registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/huawei/huawei_adapter.go:42]: the factory of Huawei adapter was registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/googlegcr/adapter.go:35]: the factory for adapter google-gcr registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/awsecr/adapter.go:43]: the factory for adapter aws-ecr registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/azurecr/adapter.go:15]: Factory for adapter azure-acr registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/aliacr/adapter.go:31]: the factory for adapter ali-acr registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/jfrog/adapter.go:47]: the factory of jfrog artifactory adapter was registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/quay/adapter.go:55]: the factory of Quay adapter was registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/helmhub/adapter.go:30]: the factory for adapter helm-hub registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/gitlab/adapter.go:17]: the factory for adapter gitlab registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/dtr/adapter.go:22]: the factory of dtr adapter was registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/artifacthub/adapter.go:30]: the factory for adapter artifact-hub registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/tencentcr/adapter.go:42]: the factory for adapter tencent-tcr registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/pkg/reg/adapter/githubcr/adapter.go:29]: the factory for adapter github-ghcr registered
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/core/controllers/base.go:157]: Config path: /etc/core/app.conf
Sep 3 23:06:31 172.19.0.1 core[740]: 2021-09-03T23:06:31Z [INFO] [/core/main.go:163]: initializing cache ...
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/core/main.go:170]: initializing configurations...
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/lib/config/systemconfig.go:197]: key path: /etc/core/key
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/lib/config/config.go:98]: init secret store
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/core/main.go:172]: configurations initialization completed
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/common/dao/base.go:65]: Registering database: type-PostgreSQL host-postgresql port-5432 database-registry sslmode-"disable"
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/common/dao/base.go:70]: Register database completed
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/common/dao/pgsql.go:127]: Upgrading schema for pgsql ...
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/common/dao/pgsql.go:130]: No change in schema, skip.
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/migration/migration.go:58]: Abstracting artifact data to DB...
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/migration/migration.go:67]: No need to abstract artifact data. Skip
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/core/main.go:84]: User id: 1 already has its encrypted password.
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/chartserver/cache.go:185]: Enable redis cache for chart caching
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/chartserver/reverse_proxy.go:60]: New chart server traffic proxy with middlewares
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/core/api/chart_repository.go:621]: API controller for chart repository server is successfully initialized
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/core/main.go:262]: Removing Trivy scanner
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/core/main.go:218]: initializing notification...
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/pkg/notification/notification.go:44]: notification initialization completed
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/core/main.go:237]: Version: v2.3.1, Git commit: 1058f33
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/core/main.go:239]: Fix empty subiss for meta info data.
Sep 3 23:06:32 172.19.0.1 core[740]: 2021-09-03T23:06:32Z [INFO] [/pkg/oidc/fix.go:23]: Not found any records with empty subiss, good to go.
Sep 3 23:06:32 172.19.0.1 core[740]: 2021/09/03 23:06:32.514 #33[1;34m[I]#33[0m [asm_amd64.s:1374] http server Running on http://:8080
Sep 3 23:08:37 172.19.0.1 core[740]: 2021-09-03T23:08:37Z [INFO] [/controller/registry/controller.go:221]: Start regular health check for registries with interval 5m0s

[ZrytyADHD]

I have the same problem updating from 2.2.0 to 2.3.0.
After update I get empty DB and all setting including ldap.
Trying make it one more time same effect.
Revert snapshot and update again give me the same error.

OS RHEL 7.9

On Centos 7.9 upgrade go without problems.

[electrical]

According to the release notes https://github.com/goharbor/harbor/releases/tag/v2.3.0

Upgrade Considerations
During upgrade, Harbor will remove the old Postgres data and migrate it to new destination to compatible new version postgres.
Please back up your data before upgrading to v2.3.0.

It would have been nice if they mentioned this also in the subsequent releases ( 2.3.1 and 2.3.2 ).
The thing i'm really missing is a backup script or some documentation on things like database names so we know what to backup.

[electrical]

An other thing I've noticed when upgrading with Helm, is that all the names have changed causing all kinds of new volumes to be created.

[electrical]

Seems I hit this issue: goharbor/harbor-helm#987 following the adviced solution solved it for me.
It nicely upgraded the database as well.

[wy65701436]

@strajansebastian can you share the postgres log on the failure step?

[ZrytyADHD]

Hey I got the solution for that.
Resolving this problem is simple even if someone install already 2.30 or 2.3.2 with empty db.
First I describe update from 2.x.x to 2.3.x
Steps:

1. Download the 2.3.0 or 2.3.2 harbor installer online or offline unpack it and migration image
2. Copy from previous version harbor.yml file to folder with new version
3. Migrate it with docker image to version which you want to install
4. Change name of your Harbor data folder - in my example i change it from data to harbor_data
5. Edit previously copied file harbor.yml and find line
   #The default data volume
   data_volume: /data
   change it to you new data folder name:
   data_volume: /harbor_data
6. Use the installer ./prepare nad next ./install.sh with you specific parameters
7. Check Harbor it shoud be working

Sometimes after start Harbor show "Core service is not working" error. If you see that shutdown harbor with docker-compose down and start it again with docker-compose up -d

2nd option is for people which already update and get clean db
1.Change name of you Harbor data folder - in my example i change it from data to harbor_data
2. Edit previously copied file harbor.yml and find line
#The default data volume
data_volume: /data
change it to your new data folder name:
data_volume: /harbor_data
3. Use the installer ./prepare nad next ./install.sh with you specific parameters
4. Check Harbor it shoud be working

The problem with empty database only occur when someone use default /data folder as location for harbor files. With custom data folder name problem is never show up.

[wy65701436]

@ZrytyADHD what's the error did you encounter on upgrading? If possible, please share the postgres.log, we got user report some permission error on specific os, and you can try with the workaround. #15464 (comment)

[ZrytyADHD]

Log from postgresql.log System is RHEL 8.4 Log is from failed upgrade.
Sep 7 11:49:18 172.18.0.1 postgresql[1321]: LOG: database system was shut down at 2021-09-07 09:49:17 UTC
Sep 7 11:49:18 172.18.0.1 postgresql[1321]: LOG: MultiXact member wraparound protections are now enabled
Sep 7 11:49:18 172.18.0.1 postgresql[1321]: LOG: database system is ready to accept connections
Sep 7 11:49:18 172.18.0.1 postgresql[1321]: LOG: autovacuum launcher started
Sep 7 11:51:26 172.18.0.1 postgresql[1321]: LOG: received smart shutdown request
Sep 7 11:51:26 172.18.0.1 postgresql[1321]: LOG: autovacuum launcher shutting down
Sep 7 11:51:26 172.18.0.1 postgresql[1321]: LOG: shutting down
Sep 7 11:51:26 172.18.0.1 postgresql[1321]: LOG: database system is shut down
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: The files belonging to this database system will be owned by user "postgres".
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: This user must also own the server process.
Sep 7 11:53:00 172.19.0.1 postgresql[1321]:
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: The database cluster will be initialized with locales
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: COLLATE: en_US.UTF-8
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: CTYPE: en_US.UTF-8
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: MESSAGES: C
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: MONETARY: C
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: NUMERIC: C
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: TIME: C
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: The default text search configuration will be set to "english".
Sep 7 11:53:00 172.19.0.1 postgresql[1321]:
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: Data page checksums are disabled.
Sep 7 11:53:00 172.19.0.1 postgresql[1321]:
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: creating directory /var/lib/postgresql/data/pg13 ... ok
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: creating subdirectories ... ok
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: selecting dynamic shared memory implementation ... posix
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: selecting default max_connections ... 100
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: selecting default shared_buffers ... 128MB
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: selecting default time zone ... UTC
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: creating configuration files ... ok
Sep 7 11:53:00 172.19.0.1 postgresql[1321]: running bootstrap script ... ok
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: performing post-bootstrap initialization ... ok
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: syncing data to disk ... ok
Sep 7 11:53:01 172.19.0.1 postgresql[1321]:
Sep 7 11:53:01 172.19.0.1 postgresql[1321]:
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: Success. You can now start the database server using:
Sep 7 11:53:01 172.19.0.1 postgresql[1321]:
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: pg_ctl -D /var/lib/postgresql/data/pg13 -l logfile start
Sep 7 11:53:01 172.19.0.1 postgresql[1321]:
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: initdb: warning: enabling "trust" authentication for local connections
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: You can change this by editing pg_hba.conf or using the option -A, or
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: --auth-local and --auth-host, the next time you run initdb.
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: postgres
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: waiting for server to start....2021-09-07 09:53:01.627 UTC [20] LOG: starting PostgreSQL 13.3 on x86_64-unknown-linux-gnu, compiled by x86_64-unknown-linux-gnu-gcc (GCC) 10.2.0, 64-bit
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:01.633 UTC [20] LOG: listening on Unix socket "/run/postgresql/.s.PGSQL.5432"
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:01.657 UTC [21] LOG: database system was shut down at 2021-09-07 09:53:01 UTC
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:01.663 UTC [20] LOG: database system is ready to accept connections
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: done
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: server started
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: ALTER ROLE
Sep 7 11:53:01 172.19.0.1 postgresql[1321]:
Sep 7 11:53:01 172.19.0.1 postgresql[1321]:
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: waiting for server to shut down....2021-09-07 09:53:01.719 UTC [20] LOG: received fast shutdown request
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:01.724 UTC [20] LOG: aborting any active transactions
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:01.725 UTC [20] LOG: background worker "logical replication launcher" (PID 27) exited with exit code 1
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:01.725 UTC [22] LOG: shutting down
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:01.778 UTC [20] LOG: database system is shut down
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: done
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: server stopped
Sep 7 11:53:01 172.19.0.1 postgresql[1321]:
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: PostgreSQL init process complete; ready for start up.
Sep 7 11:53:01 172.19.0.1 postgresql[1321]:
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: waiting for server to start....LOG: database system was shut down at 2021-09-07 09:51:26 UTC
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: LOG: MultiXact member wraparound protections are now enabled
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: LOG: database system is ready to accept connections
Sep 7 11:53:01 172.19.0.1 postgresql[1321]: LOG: autovacuum launcher started
Sep 7 11:53:02 172.19.0.1 postgresql[1321]: done
Sep 7 11:53:02 172.19.0.1 postgresql[1321]: server started
Sep 7 11:53:02 172.19.0.1 postgresql[1321]: waiting for server to shut down....LOG: received fast shutdown request
Sep 7 11:53:02 172.19.0.1 postgresql[1321]: LOG: aborting any active transactions
Sep 7 11:53:02 172.19.0.1 postgresql[1321]: LOG: autovacuum launcher shutting down
Sep 7 11:53:02 172.19.0.1 postgresql[1321]: LOG: shutting down
Sep 7 11:53:02 172.19.0.1 postgresql[1321]: LOG: database system is shut down
Sep 7 11:53:03 172.19.0.1 postgresql[1321]: done
Sep 7 11:53:03 172.19.0.1 postgresql[1321]: server stopped
Sep 7 11:53:03 172.19.0.1 postgresql[1321]: start to upgrade.
Sep 7 11:53:03 172.19.0.1 postgresql[1321]: Performing Consistency Checks
Sep 7 11:53:03 172.19.0.1 postgresql[1321]: -----------------------------
Sep 7 11:53:03 172.19.0.1 postgresql[1321]: Checking cluster versions ok
Sep 7 11:53:04 172.19.0.1 postgresql[1321]: Checking database user is the install user ok
Sep 7 11:53:04 172.19.0.1 postgresql[1321]: Checking database connection settings ok
Sep 7 11:53:04 172.19.0.1 postgresql[1321]: Checking for prepared transactions ok
Sep 7 11:53:04 172.19.0.1 postgresql[1321]: Checking for system-defined composite types in user tables ok
Sep 7 11:53:04 172.19.0.1 postgresql[1321]: Checking for reg* data types in user tables ok
Sep 7 11:53:04 172.19.0.1 postgresql[1321]: Checking for contrib/isn with bigint-passing mismatch ok
Sep 7 11:53:04 172.19.0.1 postgresql[1321]: Checking for tables WITH OIDS ok
Sep 7 11:53:05 172.19.0.1 postgresql[1321]: Checking for invalid "sql_identifier" user columns ok
Sep 7 11:53:05 172.19.0.1 postgresql[1321]: Checking for invalid "unknown" user columns ok
Sep 7 11:53:05 172.19.0.1 postgresql[1321]: Creating dump of global objects ok
Sep 7 11:53:05 172.19.0.1 postgresql[1321]: Creating dump of database schemas
Sep 7 11:53:05 172.19.0.1 postgresql[1321]: notaryserver
Sep 7 11:53:05 172.19.0.1 postgresql[1321]: notarysigner
Sep 7 11:53:05 172.19.0.1 postgresql[1321]: postgres
Sep 7 11:53:05 172.19.0.1 postgresql[1321]: registry
Sep 7 11:53:05 172.19.0.1 postgresql[1321]: template1
Sep 7 11:53:05 172.19.0.1 postgresql[1321]: ok
Sep 7 11:53:06 172.19.0.1 postgresql[1321]: Checking for presence of required libraries ok
Sep 7 11:53:06 172.19.0.1 postgresql[1321]: Checking database user is the install user ok
Sep 7 11:53:06 172.19.0.1 postgresql[1321]: Checking for prepared transactions ok
Sep 7 11:53:06 172.19.0.1 postgresql[1321]: Checking for new cluster tablespace directories ok
Sep 7 11:53:06 172.19.0.1 postgresql[1321]:
Sep 7 11:53:06 172.19.0.1 postgresql[1321]: If pg_upgrade fails after this point, you must re-initdb the
Sep 7 11:53:06 172.19.0.1 postgresql[1321]: new cluster before continuing.
Sep 7 11:53:06 172.19.0.1 postgresql[1321]:
Sep 7 11:53:06 172.19.0.1 postgresql[1321]: Performing Upgrade
Sep 7 11:53:06 172.19.0.1 postgresql[1321]: ------------------
Sep 7 11:53:06 172.19.0.1 postgresql[1321]: Analyzing all rows in the new cluster ok
Sep 7 11:53:06 172.19.0.1 postgresql[1321]: Freezing all rows in the new cluster ok
Sep 7 11:53:07 172.19.0.1 postgresql[1321]: Deleting files from new pg_xact ok
Sep 7 11:53:07 172.19.0.1 postgresql[1321]: Copying old pg_clog to new server ok
Sep 7 11:53:07 172.19.0.1 postgresql[1321]: Setting next transaction ID and epoch for new cluster ok
Sep 7 11:53:07 172.19.0.1 postgresql[1321]: Deleting files from new pg_multixact/offsets ok
Sep 7 11:53:07 172.19.0.1 postgresql[1321]: Copying old pg_multixact/offsets to new server ok
Sep 7 11:53:07 172.19.0.1 postgresql[1321]: Deleting files from new pg_multixact/members ok
Sep 7 11:53:07 172.19.0.1 postgresql[1321]: Copying old pg_multixact/members to new server ok
Sep 7 11:53:07 172.19.0.1 postgresql[1321]: Setting next multixact ID and offset for new cluster ok
Sep 7 11:53:07 172.19.0.1 postgresql[1321]: Resetting WAL archives ok
Sep 7 11:53:07 172.19.0.1 postgresql[1321]: Setting frozenxid and minmxid counters in new cluster ok
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: Restoring global objects in the new cluster ok
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: Restoring database schemas in the new cluster
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: template1
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: notaryserver
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: notarysigner
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: postgres
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: registry
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: ok
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: Copying user relation files
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: /var/lib/postgresql/data/base/16384/2613
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: /var/lib/postgresql/data/base/16384/2683
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: /var/lib/postgresql/data/base/16386/2613
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: /var/lib/postgresql/data/base/16386/2683
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: /var/lib/postgresql/data/base/12406/2613
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: /var/lib/postgresql/data/base/12406/2683
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: /var/lib/postgresql/data/base/16388/2613
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: /var/lib/postgresql/data/base/16388/2683
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: /var/lib/postgresql/data/base/16388/16389
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: /var/lib/postgresql/data/base/16388/16392
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: /var/lib/postgresql/data/base/1/2613
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: /var/lib/postgresql/data/base/1/2683
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: ok
Sep 7 11:53:08 172.19.0.1 postgresql[1321]: Setting next OID for new cluster ok
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: Sync data directory to disk ok
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: Creating script to analyze new cluster ok
Sep 7 11:53:09 172.19.0.1 postgresql[1321]:
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: WARNING: new data directory should not be inside the old data directory, e.g. /var/lib/postgresql/data
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: Checking for hash indexes ok
Sep 7 11:53:09 172.19.0.1 postgresql[1321]:
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: Upgrade Complete
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: ----------------
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: Optimizer statistics are not transferred by pg_upgrade so,
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: once you start the new server, consider running:
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: ./analyze_new_cluster.sh
Sep 7 11:53:09 172.19.0.1 postgresql[1321]:
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: Could not create a script to delete the old cluster's data files
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: because user-defined tablespaces or the new cluster's data directory
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: exist in the old cluster directory. The old cluster's contents must
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: be deleted manually.
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: success to upgrade.
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: remove the /var/lib/postgresql/data after upgrade success.
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:09.397 UTC [1] LOG: starting PostgreSQL 13.3 on x86_64-unknown-linux-gnu, compiled by x86_64-unknown-linux-gnu-gcc (GCC) 10.2.0, 64-bit
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:09.397 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:09.397 UTC [1] LOG: listening on IPv6 address "::", port 5432
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:09.436 UTC [1] LOG: listening on Unix socket "/run/postgresql/.s.PGSQL.5432"
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:09.461 UTC [265] LOG: database system was shut down at 2021-09-07 09:53:09 UTC
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:09.462 UTC [267] FATAL: the database system is starting up
Sep 7 11:53:09 172.19.0.1 postgresql[1321]: 2021-09-07 09:53:09.485 UTC [1] LOG: database system is ready to accept connections

[wy65701436]

indeed, it's a OS specific issue, the permission of data directory is not correctly set. But, from the log, it seems that the upgrade is performed successfully, did you fix the permission?

add privileged: true can bypass it.

[ZrytyADHD]

No I don't In my case change data folder name and reinstalling harbor help as I mentioned in previous comment
After failed upgrade permistion to data folder is
drwx polkitd input
the same is for pg132 folder and files

[ZrytyADHD]

I make some research and I found this issue don't need to be a OS related.
In my second instance where data folder from begining was named data_harbor not default data upgrade to 2.3.2 is going without issue on the same OS RHEL 8.4.
I also install on the same system another harbor 2.0 with default data folder name and always get this issue when updating to 2.3.2

[dajeffers]

I was able to resolve this by updating docker-ce and docker-ce-cli to 20.10.8.

[ZrytyADHD]

Hey I can confirm I use docker-ce v 18 on server which have an issue and docker v20 on serwer without this.