SSC Seeding error when upgrading to 24.4

Hi,

I am currently updating our SSC server from 23.1 to 24.4 and facing the following seeding error. I generated sql migration script and ran it against our DB before I started the seed bundles.

This happens when I seed "Fortify_Process_Seed_Bundle-2024_Q2_0006.zip" file. I haven't ran any other seed bundles due to this error

2024-12-10 13:30:12,421 [INFO] com.fortify.manager.DAL.HibernateDatabaseInterface - Using JDBC driver MariaDB Connector/J [3.1.4], connecting to MySQL [8.0.35]
2024-12-10 13:30:16,881 [WARN] com.fortify.manager.service.scheduler.NullSchedulerServiceImpl - Null scheduler service instance, analysis trace refresh not scheduled
2024-12-10 13:31:21,488 [WARN] org.mariadb.jdbc.message.server.ErrorPacket - Error: 1062-23000: Duplicate entry '22-85155-3' for key 'user_pi.PRIMARY'
2024-12-10 13:31:21,489 [WARN] org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 1062, SQLState: 23000
2024-12-10 13:31:21,489 [ERROR] org.hibernate.engine.jdbc.spi.SqlExceptionHelper - (conn=159) Duplicate entry '22-85155-3' for key 'user_pi.PRIMARY'
2024-12-10 13:31:26,009 [INFO] com.fortify.manager.service.objectstorage.ObjectStorageMigrationServiceImpl - Ignoring request to stop object storage migration - it is not running or stop has already been requested.
2024-12-10 13:31:26,036 [ERROR] com.fortify.ssc.init.endpoints.AppInitDatabaseOperationsController - Unable to seed all init seed bundles.
com.fortify.ssc.init.SeedingException: Unable to seed all init seed bundles.
at com.fortify.ssc.init.SeedContextProvider.seedInitBundles(SeedContextProvider.java:114) ~[ssc-init-24.4.0.0336.jar:?]
at com.fortify.ssc.init.endpoints.AppInitDatabaseOperationsController.lambda$seed$2(AppInitDatabaseOperationsController.java:270) ~[ssc-init-24.4.0.0336.jar:?]
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.base/java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: com.fortify.manager.exception.FMDALGeneralException: An unexpected error occurred.

ssc_seeding log:

2024-12-10 13:30:18,307 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Opening seed bundle: ConfPropertiesSeedBundle.zip
2024-12-10 13:30:18,308 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2024-12-10 13:30:18,333 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Seeding bundle ConfigProperties version 24.4.0
2024-12-10 13:30:18,333 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: ConfProperties.xml
2024-12-10 13:30:18,460 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Opening seed bundle: ExternalMetadataSeedBundle.zip
2024-12-10 13:30:18,461 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2024-12-10 13:30:18,469 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Seeding bundle Metadata version 24.4.0
2024-12-10 13:30:18,469 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: Metadata.xml
2024-12-10 13:31:19,436 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Opening seed bundle: UserSeedBundle.zip
2024-12-10 13:31:19,437 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: SeedBootstrap.xml
2024-12-10 13:31:19,494 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Seeding bundle Master version 8.70
2024-12-10 13:31:19,494 [pool-2-thread-1] INFO com.fortify.manager.BLL.impl.SeedManagerImpl - Loading entry: PermissionUsers.xml

Tomcat version: 9.0.95

OS: RHEL 8

JDK: openjdk version "17.0.9" 2023-10-17 LTS

DB: Mysql 8

Tried several times with a fresh DB(23.1) and with a fresh install of a SSC in a newly created RHEL server but no luck

Any pointers on this?