APAR status
Closed as program error.
Error description
Kubectl get pods will show that some pods/containers are pending. Looking at the describe output for that pod, the events will contain a message like the following: Warning FailedScheduling 61s (x4 over 3m39s) default-scheduler 0/1 nodes are available: 1 Insufficient cpu.
Local fix
Problem summary
The pods would fail to start when only 2 CPU were available to the analytics OVA due to CPU starvation. This issue has been resolved as part of the analytics rearchitecture work that happened in APIC 10.0.5 and all pods now start even when only given 2CPU.
Problem conclusion
Fix targeted at 10.0.5.1
Temporary fix
Comments
APAR Information
APAR number
LI82151
Reported component name
API CONNECT ENT
Reported component ID
5725Z2201
Reported release
A0X
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-05-11
Closed date
2022-09-22
Last modified date
2022-09-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
API CONNECT ENT
Fixed component ID
5725Z2201
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
24 September 2022