mssql server fails to start due to incomplete/out of sequence CPUs

.Insufficient CPUs Some {osc-operator} pods use container CPU resource limits to increase the number of available CPUs for the pod. These pods might receive fewer CPUs than requested. If the functionality is available inside the container, you can diagnose CPU resource issues by using `oc rsh <pod>` to access a pod and 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 will likely change unpredictably from run to run. As a workaround, you can use a pod annotation to request additional CPUs rather than setting a CPU limit. CPU requests that use pod annotation are not affected by this issue, because the processor allocation method is different. Rather than setting a CPU limit, the following annotation must be added to the metadata of the pod: [source,yaml] ---- metadata:   annotations:     io.katacontainers.config.hypervisor.default_vcpus: "16" ----