.Increasing container CPU resource limits fails if CPUs are offline Using container CPU resource limits to increase the number of available CPUs for a pod fails if the requested CPUs are offline. If the functionality is available, you can diagnose CPU resource issues by running the `oc rsh <pod>` command to access a pod and then running the `lscpu` command: [source,terminal] ---- $ lscpu ---- Example output: [source,terminal] ---- CPU(s): 16 On-line CPU(s) list: 0-12,14,15 Off-line CPU(s) list: 13 ---- The list of offline CPUs is unpredictable and can change from run to run. Workaround: Use a pod annotation to request additional CPUs, as in the following example: [source,yaml] ---- metadata:   annotations:     io.katacontainers.config.hypervisor.default_vcpus: "16" ----