Troubleshooting
Problem
One, or more, of the pods in the VMWare API Connect deployment are stuck in Pending state
Symptom
The upgrade fails with and "describe" of the pod shows this error:
Warning FailedScheduling 45m default-scheduler 0/1 nodes are available: 1 node(s) didn't find available persistent volumes to bind.
This error means the system might have run out of PVs, most likely due to the main subsystem CR "siteName" having changed in the past.
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":"a8m50000000L0rvAAC","label":"API Connect"}],"ARM Case Number":"TS008221088","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0.0"}]
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.
Was this topic helpful?
Document Information
Modified date:
01 February 2022
UID
ibm16551446