Harbor OVF deployment fails due to " ERROR: relation "properties" does not exist (SQLSTATE 42P01)" in harbor-core container

Products

• VMware Tanzu Kubernetes Grid Management

Issue/Introduction

• When deploying Harbor OVF for internet-restricted environments, the VM is deployed, but Harbor containers don't all come up correctly.
• The harbor-core and harbor-jobservice containers will be stuck in Restarting state.
• When viewing journalctl -xeu harbor command from the VM, users will see error messages like:

Dec 12 21:50:44 localhost docker-compose[1829]: harbor-db          | 2024-12-12 21:50:44.112 UTC [43] ERROR:  relation "properties" does not exist at character 15
Dec 12 21:50:44 localhost docker-compose[1829]: harbor-db          | 2024-12-12 21:50:44.112 UTC [43] STATEMENT:  select * from properties
Dec 12 21:50:44 localhost docker-compose[1829]: harbor-core        | 2024-12-12T21:50:44Z [FATAL] [/core/main.go:206]: failed to load config: ERROR: relation "properties" does not exist (SQLSTATE 42P01)

 

Environment

This is present in Harbor OVF deployments 2.10.3 and 2.9.x

Cause

This failure occurs when the Harbor DB password chosen has a pound sign (#) as the first character.

Resolution

Redeploy the Harbor OVF with a password that doesn't have a leading pound sign #.

Additional Information

Similar issues might present if spaces are used in the Harbor DB password. Avoid using spaces in the Harbor DB password.