APAR status
Closed as program error.
Error description
When using VMWare OVA version with deployment profile n1xc4.m32 and the VM have 4 CPUs allocated. After enable backup for Analytics server a new pod called "warehouse" will show up which cause the overall CPU become insufficient.
Local fix
Override the CPU resource for the ingestion pod to allow enough CPU for the warehouse pod to start. Here is an example that can be used: spec: template: - name: ingestion containers: - name: ingestion resources: requests: cpu: 1250m As this is a OVA environment, this override must be specified by an extra values file.
Problem summary
On OVA, when the Analytics profile is n1xc2.m16, n1xc4.m32, n3xc4.m16, or n3xc4.m32, and the number of CPUs in the Analytics node is equal to the number required by the profile, enabling backups will attempt to start the Warehouse pod. However, because there is not enough remaining CPU available to meet the Warehouse CPU request, Kubernetes fails to start it and it's left in pending state.
Problem conclusion
Analytics pod CPU requests have been minorly relabalanced to ensure there is enough capacity for warehouse to deploy. Fix targeted at 10.0.8.1
Temporary fix
Comments
APAR Information
APAR number
LI83263
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
2024-10-09
Closed date
2024-11-12
Last modified date
2024-11-12
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":"BU048","label":"IBM Software"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]
Document Information
Modified date:
12 November 2024