VIP Authhub: Dataseed pod is failing and not getting started during upgrade

Products

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

Issue/Introduction

During VIP Authhub upgrade, Dataseed pod can not start.

kubectl get pods -n <NAMESPACE>

NAME                                                      READY   STATUS       RESTARTS   AGE

ssp-ssp-dataseed-job-<podname>          0/1        Init:Error                0          3m53s

Environment

Operating System: AWS, EKS kubernetes 1.29
Vip auth hub version: 2.2.5 upgrade to 3.1 

Aurora PostgreSQL: 14.5

Cause

VIP Authhub dataseed job did not complete and with error.

kubectl logs ssp-ssp-dataseed-job-<podname> -n <NAMESPACE> -c <CONTAINER>

yyyy-mm-ddT17:34:00.217Z ERROR 1 --- [main] c.b.l.FlywayMigration                    : Attempting DB migration repair
yyyy-mm-ddT17:34:00.685Z  INFO 1 --- [main] o.f.c.i.s.JdbcTableSchemaHistory    : Repair of failed migration in Schema History table "iamauth"."flyway_schema_history" not necessary. No failed migration detected.
yyyy-mm-ddT17:34:00.794Z  INFO 1 --- [main] o.f.c.i.s.JdbcTableSchemaHistory    : Repairing Schema History table for version 1.84 (Description: AlterAppAddProperties, Type: SQL, Checksum: -1276727935)  ...
yyyy-mm-ddT17:34:00.888Z ERROR 1 --- [main] c.b.l.FlywayMigration                    : DB migration repair failed with error 'Unable to repair Schema History table "iamauth"."flyway_schema_history" for version 1.84
----------------------------------------------------------------------------------------
SQL State  : 25006
Error Code : 0
Message    : ERROR: cannot execute UPDATE in a read-only transaction

Resolution

In this upgrade deployment, a working VIP Authhub Database is already created and replicated.

When upgrade to newer version, Database Schema may need update.

Please ensure user account used to perform the DB operations has DB writing permission and drSite: false in the yaml file if drSite option is used.