PBMS deployment issue – pbms-keymanager pod crashes (key_alias table missing, dbinit job not created)

PBMS
1

Hi team,

I’ve attempted to deploy the OpenG2P PBMS module from scratch twice using the official Helm chart, but I’m consistently facing critical issues during startup:

  • The pbms-keymanager pod crashes with: relation "key_alias" does not exist.
  • The pbms-keymanager-dbinit job, which is expected to create the necessary DB tables (like key_alias), is not created at all during deployment.
  • I’ve verified that dbInit.enabled=true and even tried forcing Helm to re-trigger the init job, but the job still doesn’t get deployed.
  • Other services like mock-identity-system are also failing due to similar DB initialization issues.

This happens consistently even after:

  • Full reinstallation,
  • Proper secret configuration,
  • Verifying Postgres access.

I suspect there may be a missing Helm hook or bug in the chart.

Could you please help me debug this further, or confirm if this is a known issue?
I have logs, Helm status outputs, and Postgres shell access available if needed.
Thanks.

2

Hi Bhavani_Shankar,

Can you tell me which version of the PBMS Helm chart you are using?

Thanks!

3

Hi pramod_Belal

I’ve checked, and we are currently using the PBMS Helm chart version 2.0.2 (latest available from the OpenG2P chart repo).

Thanks!

4

Bhavani_Shankar,

Ok, you can reinstall PBMS, but before that I suggest following the uninstallation procedure from the documentation attached below. The issue might be that during the previous reinstall attempt you did not clear all the PVCs and PVs related to PBMS. Can you try this once and get back to us?

Thanks!