IDSP 4.0.2 Helm Upgrade Fails with "column vhe1_0.access_type does not exist" Due to Incorrectly Tagged ssp-db-initializer Image

Products

• Symantec Identity Security Platform - IDSP (formerly VIP Authentication Hub)

Issue/Introduction

When running helm upgrade from IDSP 4.0.1 to 4.0.2, the dataseed job fails with the following errors:

{"level":"warn","msg":"SQL Error: 0, SQLState: 42703"}
{"level":"error","msg":"ERROR: column vhe1_0.access_type does not exist\n  Position: 25"}
[...]
{"level":"error","msg":"A critical error occurred during deployment validation: Bootstrap (dataseed): Version '3.5.0' from the Maintenance table is invalid for a new install. Exiting."}
{"level":"info","msg":"Assumed deployment type: New Install (0 tenants)"}

Environment

• IDSP 4.0.2
• OpenShift

Cause

The ssp-db-initializer image pushed to the container registry and tagged as 4.0.2.1075 is actually version 4.0.1-1015, as confirmed in the dataseed pod logs:

{"msg":"Starting SspDbInitializerApplication v4.0.1-1015 using Java 21.0.9 ..."}

Because the initializer runs with an older image, it detects a schema mismatch (access_type column missing) and incorrectly assumes a fresh install, causing the bootstrap validation to fail.

To confirm the image version currently in use, run the following on the OpenShift environment:

# oc logs <releasename>-ssp-dataseed-job-<id> -c ssp-db-init | head -10

Resolution

Re-push the correct ssp-db-initializer:4.0.2.1075 image to the local container registry, then re-run the helm upgrade command.

Ensure all IDSP component images are properly tagged before pushing to the registry. Refer to the official upgrade documentation for the complete list of required images and their expected versions (1)(2). 

Additional Information

1. Upgrading Symantec Identity Security Platform
   
   
2. Identity Security Platform - 4.0