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

OpenShift Sandboxed Container pods utilizing container CPU resource limits to increase the number of available CPUs for the pod may receive fewer CPUs than requested. This can be diagnosed by `oc rsh <pod>` and running `lscpu`, if that functionality is available inside the container. For example: # lscpu CPU(s): 16 On-line CPU(s) list: 0-12,14,15 Off-line CPU(s) list: 13 The list of available off-line CPUs will likely change from run to run in an unpredictable manner. A workaround is to use a pod annotation to request additional CPUs rather than a CPU limit; the method of allocating processors is different, and CPUs requested by means of pod annotation are not subject to this issue. The following should be added to the pod's metadata: metadata:   annotations:     io.katacontainers.config.hypervisor.default_vcpus: "16" and a CPU limit not used.