APAR status
Closed as program error.
Error description
In the Kubernetes describe output for some pods, you might see the event messages similar to the following: Warning FailedScheduling 17m (x3 over 32m) default-scheduler 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
Local fix
we can reduce this to 96MB by adding a template override to the extra-values file: extra-values.yaml: spec: template: - name: osinit containers: - name: osinit resources: requests: memory: 96Mi Once this has been added to the extra-values file, it should be possible to re-run the apicup install command to allow the upgrade to complete.
Problem summary
<p>If deploying or upgrading using a large deployment profile on VMware, the install/upgrade process does not finish successfully.</p>
Problem conclusion
<p>A fix is targeted for API Connect version 10.0.5.5.</p>
Temporary fix
Comments
APAR Information
APAR number
LI83057
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
2023-09-19
Closed date
2023-10-23
Last modified date
2023-10-23
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 October 2023