You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "mnmami (via GitHub)" <gi...@apache.org> on 2025/08/21 06:51:31 UTC

[I] error: no migration found for version 26 [superset]

mnmami opened a new issue, #34786:
URL: https://github.com/apache/superset/issues/34786

   ### Bug description
   
   On Helm chart deployment to a GKE cluster, I'm encountering this error from **langfuse-web** pod:
   ```
   Script executed successfully.                                                                                            │ 10.196.13.145  gke-dam-dev-gke-m │
   │ Prisma schema loaded from packages/shared/prisma/schema.prisma                                                           │──────────────────────────────────┘
   │ Datasource "db": PostgreSQL database "langfuse_db", schema "public" at "langfuse-postgresql"                             │                                   
   │                                                                                                                          │                                   
   │ 327 migrations found in prisma/migrations                                                                                │
   │                                                                                                                          │
   │                                                                                                                          │
   │ No pending migrations to apply.                                                                                          │
   │ error: no migration found for version 26: read down for version 26 .: file does not existerror: no migration found for v │
   │ Applying clickhouse migrations failed. This is mostly caused by the database being unavailable.                          │
   │ Exiting... 
   ```
   
   The issue occurs both when using the bundled Clickhouse, Redis, Postgres and MinIO and using these as external services.
   
   Here are my custom Helm values of the former case (keep the bundled services):
   
   ```
   langfuse:
   
     image:
       # -- The image tag to use for all langfuse deployments. Can be overridden by the individual deployments. Falls back to appVersion if not set.
       tag: 3.97.5
   
     server:
       service:
         type: LoadBalancer
         port: 3000
   
     salt:
       secretKeyRef:
         name: langfuse-secrets
         key: salt
   
     encryptionKey:
       secretKeyRef:
         name: langfuse-secrets
         key: encryption-key
   
     nextauth:
       url: http://localhost:3000
       secret:
         secretKeyRef:
           name: langfuse-secrets
           key: nextauth-secret
   
     ingress:
       enabled: false
       hosts:
       - host: langfuse.humainity.dev
         paths:
         - path: /
           pathType: Prefix
       annotations:
         nginx.ingress.kubernetes.io/ssl-redirect: "true"
         cert-manager.io/cluster-issuer: letsencrypt-prod
       tls:
         enabled: false
         secretName: "langfuse-tls"
   
     worker:
       pod:
         additionalEnv:
           - name: REDIS_PORT
             value: 6379
    
   clickhouse:
     deploy: true
     auth:
       existingSecret: langfuse-secrets
       existingSecretKey: clickhouse-password
   
   postgresql:
     deploy: true
     auth:
       username: langfuse_user
       database: langfuse_db
       existingSecret: langfuse-secrets
       secretKeys:
         userPasswordKey: postgresql-password
   
   redis:
     deploy: true
     auth:
       existingSecret: langfuse-secrets
       existingSecretPasswordKey: redis-password
   
     host: redis.data-platform.svc.cluster.local
     port: 6379
   
   s3:
     deploy: true
     auth:
       existingSecret: langfuse-secrets
       rootUserSecretKey: minio-rootuser
       rootPasswordSecretKey: minio-rootuser-password
   
     bucket: "langfuse-bucket"
     region: "me-dammam"
     endpoint: "http://minio:9000"
     forcePathStyle: true
     accessKeyId:
       value: "minioadmin"
     secretAccessKey:
       value: "minioadmin123"
     eventUpload:
       prefix: "events/"
     batchExport:
       prefix: "exports/"
     mediaUpload:
       prefix: "media/"
   ```
   
   I tried multiple versions from latest 3.99.0 to 3.97.0.
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Not applicable
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
   - [ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
   - [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] error: no migration found for version 26 [superset]

Posted by "mnmami (via GitHub)" <gi...@apache.org>.
mnmami closed issue #34786: error: no migration found for version 26
URL: https://github.com/apache/superset/issues/34786


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org