Dirty database version 7. Fix and force version.

[gzwxh]

Reference document:https://docs.px.dev/installing-pixie/install-guides/self-hosted-pixie/
After deployment, the service startup encountered an error, and the error log is:
[root@master pixie]# kubectl get pods -n plc
vzmgr-server-856dd957d9-pn47z 0/1 CrashLoopBackOff 9 (3m26s ago) 20m
[root@master pixie]#
[root@master pixie]# kubectl logs -n plc vzmgr-server-856dd957d9-pn47z
time="2025-07-21T01:49:02Z" level=info msg="Starting service" service=vzmgr-service version=0.1.9+Distribution.534b892.20250124234745.1.jenkins
time="2025-07-21T01:49:02Z" level=info msg="Setting up database" db_hostname=postgres.plc.svc.cluster.local db_name=pl db_port=5432 db_username=pl
time="2025-07-21T01:49:02Z" level=info msg="Connected to Postgres"
time="2025-07-21T01:49:02Z" level=fatal msg="Failed to apply migrations" error="Dirty database version 7. Fix and force version."

postgres The version has been replaced, but the error message remains the same。

[ddelnano]

Hey @gzwxh, thanks for the bug report. There seems to be a situation where the database migrations run on service start up don't run cleanly. I've seen reports of this before, and I'm not sure what causes it at this time.

The current remediation is to delete postgres's PVC and restart all of the services within the plc namespace. It should apply cleanly on the next time it's triggered.

Please attach your postgres container logs if you still have them. I'll also try to reproduce this and triage the problem soon.