The error “Unknown migration type 'SPRING_JDBC' found in schema history” happened during upgrading to opsman 3.3.0. or 3.2.6 or 3.1.10

Products

• VMware Tanzu Platform Core

Issue/Introduction

The apply change failed on bosh director.

Failed deploying (00:19:21)
Cleaning up rendered CPI jobs... Finished (00:00:00)
Deploying:
 Running the post-start script:
   Sending 'get_task' to the agent:
     Agent responded with error: Action Failed get_task: Task ###### result: 1 of 4 post-start scripts failed. Failed Jobs: credhub. Successful Jobs: nats, director, uaa.
Exit code 1

 

bosh/0:~# monit summary

The Monit daemon 5.2.5 uptime: 2h 3m
Process 'nats'                      running

Process 'bosh_nats_sync'            running

Process 'postgres'                  running

Process 'director'                  running

Process 'worker_1'                  running

Process 'worker_2'                  running

Process 'worker_3'                  running

Process 'worker_4'                  running

Process 'worker_5'                  running

Process 'director_scheduler'        running

Process 'metrics_server'            running

Process 'director_sync_dns'         running

Process 'director_nginx'            running

Process 'health_monitor'            running

Process 'uaa'                       running

Process 'credhub'                   Does not exist

Process 'cpi'                       running

Process 'system-metrics-agent'      running

Process 'count-cores'               running

System 'system_########’ running

 

/var/vcap/sys/log/credhub/credhub.log

2026-04-28T01:44:15.328Z [main] ....  INFO --- FlywayExecutor: Database: jdbc:postgresql://127.0.0.1:5432/credhub?autoReconnect=true (PostgreSQL 15.17)
2026-04-28T01:44:15.701Z [main] ....  WARN --- FlywayMigrationStrategyConfiguration: Validation failed: "Unknown migration type 'SPRING_JDBC' found in schema history.
You might be missing a required extension JAR on the classpath.".
2026-04-28T01:44:15.701Z [main] ....  INFO --- FlywayMigrationStrategyConfiguration: Attempting to repair...
2026-04-28T01:44:15.704Z [main] ....  INFO --- FlywayExecutor: Database: jdbc:postgresql://127.0.0.1:5432/credhub?autoReconnect=true (PostgreSQL 15.17)
2026-04-28T01:44:15.762Z [main] .... FATAL --- FlywayMigrationStrategyConfiguration: Couldn't repair database. Crashing.
2026-04-28T01:44:15.764Z [main] ....  WARN --- AnnotationConfigServletWebServerApplicationContext: Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: Failed to initialize dependency 'flywayInitializer' of LoadTimeWeaverAware bean 'entityManagerFactory': Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Unknown migration type 'SPRING_JDBC' found in schema history.
You might be missing a required extension JAR on the classpath.

Environment

Tanzu Operations Manager 3.1.10, 3.2.6 and 3.3.0

Cause

This is a known issue introduced in credhub release 2.15.4 which impacts opsman 3.3.0, 3.2.6 and 3.1.10 https://github.com/cloudfoundry/credhub/commit/0574d2231e39d1c876c6180d77eb3709c5ed3f8c

• • Opsman 3.3.0 = director 282.1.8   | credhub 2.15.4
  • Opsman 3.2.6 = director 282.1.8   | credhub 2.15.4
  • Opsman 3.1.10 = director 282.1.8 | credhub 2.15.4

Resolution

Workaround:

• To manually update credhub database is workaround this issue.

1. Log into the credhub database on bosh director vm:

ssh -i bosh.key bbr@##.##.##.## (SSh to bosh - bbr creds from OpsMan)

2. Connect to the credhub database:

cd /var/vcap/packages/postgres-XX/bin/

./psql -U postgres -h 127.0.0.1 -d credhub

3. credhub=> select * from flyway_schema_history WHERE type = 'SPRING_JDBC';

4. credhub=> UPDATE flyway_schema_history SET type = 'JDBC' WHERE type = 'SPRING_JDBC';

5. credhub=> select * from flyway_schema_history WHERE type = 'JDBC';

6. \q

7. Run Apply changes.

 

 

Fix:

• The prefer approach is to upgrade to credhub 2.15.5 which has a fix. Will be shipped in the next opsmanager release of May (3.1.11 and 3.3.1, not a plan for 3.2.*).