Auth Hub upgrade failing on the Database seed pod

Products

• VIP Authentication Hub

Issue/Introduction

Upgrading VIP Auth Hub from 2.1 to 2.2 release resulting in the Upgrade process to fail on the DB dataseed pod .

The DB error log shows the migration is successful 

 main] c.b.l.FlywayMigration                    : DB migration completed successfully

The DB dataseed POD shows running with 0/1 available 

Cause

From the Helm upgrade command, we can see that the pre-upgrade dataseed failed with timeout since the default helm timetout is 5 minutes unless --timeout is specified in the helm upgrade command 

Resolution

From the Auth Hub upgrade guide, the --timeout=20 is required for the upgrade as indicated in the official guide 

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/vip-authentication-hub/2-2/Installing/upgrading-services.html

* To upgrade to the latest version of VIP Authentication Hub chart, run this command:

helm upgrade ${RELEASENAME} ssp_helm_charts/ssp -n ${NAMESPACE}  -f ssp-override.yaml --timeout=20m --set ssp.featureFlags.dataseed.enabled=true