IBM Support

Upgrading API Connect operator causes EDB operator and Postgres pods to update

Troubleshooting


Problem

When upgrading API Connect from 10.0.7 or 10.0.8 to a later release, the EDB operator and EDB Postgres pods will be automatically upgraded when the API Connect operator is upgraded to the new version.

Symptom

Immediately after upgrading the API Connect operator deployment to the new version, the EDB operator and EDB postgres pods will have their versions updated and will restart. This restart will happen before the API Connect management cluster is upgraded.
This output shows the EDB operator pods being restarted:
$ kubectl -n apic get po -l app.kubernetes.io/name=cloud-native-postgresql -w
NAME                            READY   STATUS    RESTARTS   AGE
edb-operator-7c4c9758b6-jfmjs   1/1     Running   1          22m
edb-operator-7c4c9758b6-lz7tv   1/1     Running   1          22m
edb-operator-7c4c9758b6-wz8tr   1/1     Running   7          36m
edb-operator-7c58d8c8db-74dcs   0/1     Pending   0          0s
edb-operator-7c58d8c8db-74dcs   0/1     Pending   0          0s
edb-operator-7c58d8c8db-74dcs   0/1     ContainerCreating   0          1s
edb-operator-7c58d8c8db-74dcs   0/1     ContainerCreating   0          1s
edb-operator-7c58d8c8db-74dcs   0/1     Running             0          2s
edb-operator-7c58d8c8db-74dcs   1/1     Running             0          11s
edb-operator-7c4c9758b6-wz8tr   1/1     Terminating         7          38m
edb-operator-7c58d8c8db-njsl7   0/1     Pending             0          0s
edb-operator-7c58d8c8db-njsl7   0/1     Pending             0          0s
edb-operator-7c58d8c8db-njsl7   0/1     ContainerCreating   0          0s
edb-operator-7c58d8c8db-njsl7   0/1     ContainerCreating   0          1s
edb-operator-7c4c9758b6-wz8tr   1/1     Terminating         7          38m
edb-operator-7c4c9758b6-wz8tr   0/1     Terminating         7          38m
edb-operator-7c58d8c8db-njsl7   0/1     Running             0          2s
edb-operator-7c4c9758b6-wz8tr   0/1     Terminating         7          38m
edb-operator-7c4c9758b6-wz8tr   0/1     Terminating         7          38m
edb-operator-7c58d8c8db-njsl7   1/1     Running             0          10s
edb-operator-7c4c9758b6-jfmjs   1/1     Terminating         1          25m
edb-operator-7c58d8c8db-sjq46   0/1     Pending             0          0s
edb-operator-7c58d8c8db-sjq46   0/1     Pending             0          0s
edb-operator-7c58d8c8db-sjq46   0/1     ContainerCreating   0          0s
edb-operator-7c4c9758b6-jfmjs   1/1     Terminating         1          25m
edb-operator-7c58d8c8db-sjq46   0/1     ContainerCreating   0          1s
edb-operator-7c58d8c8db-sjq46   0/1     Running             0          1s
edb-operator-7c4c9758b6-jfmjs   0/1     Terminating         1          25m
edb-operator-7c4c9758b6-jfmjs   0/1     Terminating         1          25m
edb-operator-7c4c9758b6-jfmjs   0/1     Terminating         1          25m
edb-operator-7c58d8c8db-sjq46   1/1     Running             0          10s
edb-operator-7c4c9758b6-lz7tv   1/1     Terminating         1          25m
edb-operator-7c4c9758b6-lz7tv   1/1     Terminating         1          25m
edb-operator-7c4c9758b6-lz7tv   0/1     Terminating         1          25m
edb-operator-7c4c9758b6-lz7tv   0/1     Terminating         1          25m
edb-operator-7c4c9758b6-lz7tv   0/1     Terminating         1          25m
This output shows the EDB postgres pods restarting:
$ kubectl -n apic get po -l app.kubernetes.io/name=management-72e1e42f-db -w
NAME                       READY   STATUS    RESTARTS   AGE
management-72e1e42f-db-1   1/1     Running   0          87s
management-72e1e42f-db-2   1/1     Running   0          2m56s
management-72e1e42f-db-3   1/1     Running   0          2m33s
management-72e1e42f-db-3   1/1     Terminating   0          4m21s
management-72e1e42f-db-3   1/1     Terminating   0          4m22s
management-72e1e42f-db-3   0/1     Terminating   0          4m23s
management-72e1e42f-db-3   0/1     Terminating   0          4m23s
management-72e1e42f-db-3   0/1     Terminating   0          4m23s
management-72e1e42f-db-3   0/1     Pending       0          0s
management-72e1e42f-db-3   0/1     Pending       0          0s
management-72e1e42f-db-3   0/1     Init:0/1      0          1s
management-72e1e42f-db-3   0/1     Init:0/1      0          2s
management-72e1e42f-db-3   0/1     Init:0/1      0          2s
management-72e1e42f-db-3   0/1     PodInitializing   0          3s
management-72e1e42f-db-3   0/1     Running           0          4s
management-72e1e42f-db-3   0/1     Running           0          7s
management-72e1e42f-db-3   0/1     Running           0          11s
management-72e1e42f-db-3   1/1     Running           0          21s
management-72e1e42f-db-1   1/1     Terminating       0          3m39s
management-72e1e42f-db-1   1/1     Terminating       0          3m39s
management-72e1e42f-db-1   0/1     Terminating       0          3m40s
management-72e1e42f-db-1   0/1     Terminating       0          3m40s
management-72e1e42f-db-1   0/1     Terminating       0          3m40s
management-72e1e42f-db-1   0/1     Pending           0          0s
management-72e1e42f-db-1   0/1     Pending           0          0s
management-72e1e42f-db-1   0/1     Init:0/1          0          0s
management-72e1e42f-db-1   0/1     Init:0/1          0          1s
management-72e1e42f-db-1   0/1     PodInitializing   0          2s
management-72e1e42f-db-1   0/1     Running           0          3s
management-72e1e42f-db-1   0/1     Running           0          5s
management-72e1e42f-db-1   0/1     Running           0          11s
management-72e1e42f-db-1   1/1     Running           0          21s
management-72e1e42f-db-2   0/1     Completed         0          5m36s
management-72e1e42f-db-2   0/1     Running           1 (2s ago)   5m37s
management-72e1e42f-db-1   1/1     Running           0            41s
management-72e1e42f-db-2   0/1     Running           1 (16s ago)   5m51s
management-72e1e42f-db-2   0/1     Running           1 (26s ago)   6m1s
management-72e1e42f-db-2   1/1     Running           1 (46s ago)   6m21s
management-72e1e42f-db-2   1/1     Terminating       1 (46s ago)   6m21s
management-72e1e42f-db-2   1/1     Terminating       1 (47s ago)   6m22s
management-72e1e42f-db-2   0/1     Terminating       1 (47s ago)   6m22s
management-72e1e42f-db-2   0/1     Terminating       1             6m23s
management-72e1e42f-db-2   0/1     Terminating       1             6m23s
management-72e1e42f-db-2   0/1     Terminating       1             6m23s
management-72e1e42f-db-2   0/1     Pending           0             0s
management-72e1e42f-db-2   0/1     Pending           0             0s
management-72e1e42f-db-2   0/1     Init:0/1          0             0s
management-72e1e42f-db-2   0/1     Init:0/1          0             1s
management-72e1e42f-db-2   0/1     Init:0/1          0             1s
management-72e1e42f-db-2   0/1     PodInitializing   0             2s
management-72e1e42f-db-2   0/1     Running           0             3s
management-72e1e42f-db-2   0/1     Running           0             5s
management-72e1e42f-db-2   0/1     Running           0             10s
management-72e1e42f-db-2   1/1     Running           0             20s
management-72e1e42f-db-2   1/1     Running           0             21s
management-72e1e42f-db-1   1/1     Running           0             95s
management-72e1e42f-db-3   1/1     Running           0             2m
management-72e1e42f-db-2   1/1     Running           0             22s
If the deployment profile uses a single-node cluster, then this will result in an outage as the database will restart and any management pods which require a connection to the database will also restart.

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":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0.7;and future releases"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
08 November 2024

UID

ibm17174570

Page Feedback