IBM Support

Stanza Creation Failure During Upgrade to API Connect v10.0.5.8

Troubleshooting


Problem

During upgrades from API Connect v10.0.5.x to v10.0.5.8, specifically for S3-only backup configurations, the stanza creation process may fail. This results in the Management subsystem entering a warning state with a WALArchiveNotWorking error, even though the upgrade completes successfully.

Symptom

Postgres database may go down and get recreated during the upgrade process.
The same S3 backup path may be reused across multiple clusters, causing WAL archiving to fail.
Example error message: 
kubectl get pods -n <namespace where APIC is deployed> | grep stanza
NAME                                                        READY   STATUS      RESTARTS   AGE
mgmt-site1-postgres-stanza-create-subin                     0/1     Error       0          4m2s

kubectl logs mgmt-site1-postgres-stanza-create-subin
....
time="timestamp" level=info msg="s3 flag enabled for backrest command"
time="timestamp" level=info msg="command to execute is [pgbackrest stanza-create  --db-host=hideme --db-path=/pgdata/mgmt-site1-postgres --repo1-type=s3]"
time="timestamp" level=info msg="output=[]"
time="timestamp" level=info msg="stderr=[ERROR: [028]: backup and archive info files exist but do not match the database\n       HINT: is this the correct stanza?\n       HINT: did an error occur during stanza-upgrade?\n]"
time="timestamp" level=fatal msg="command terminated with exit code 28"
.....

Cause

The failure is due to the reuse of the same S3 backup path across clusters, which leads to conflicts in WAL archiving metadata.

Environment

API Connect v10.0.5.x upgrading to v10.0.5.8
S3 backup configuration enabled

Diagnosing The Problem

Observe the Management subsystem entering a warning state post-upgrade.
Review logs for WAL archiving errors and stanza mismatch messages.

Resolving The Problem

To resolve the issue:
  1. Run kubectl edit mgmt <management_name>
  2. Modify the .spec.databaseBackup.path to point to a new S3 location.
  3. Set restartDB flag to true.
  4. Save the Custom Resource (CR).

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"ARM Category":[{"code":"a8mKe000000CaZWIA0","label":"API Connect-\u003EAPIC Platform - Install\/Upgrade\/Migrate"}],"ARM Case Number":"TS020020800","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0.5"}]

Document Information

Modified date:
20 August 2025

UID

ibm17242754

Page Feedback