Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-1376

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

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Medium
    • None
    • None
    • Performance / Scaling
    • True
    • Application fails to start under Kata.
    • False
    • Hide
      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.
      Show
      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.
    • Known Issue
    • Done
    • 1
    • Kata Sprint #215
    • 0
    • 0.0

    Description

      Description

      Attempt to start mssql server pod fails on OCP 4.10 -fc.0 (using the default kata installer) with fatal error in mssql server.  In 4.8.14, it succeeded.  With conventional pods, it succeeds in both releases

      Steps to reproduce

      1. Start pod using provided YAML (password and hostname elided)

      Expected result

      mssql server should start and run

      Actual result

      mssql server fails with attached error message 

      Impact

      mssql is unusable.

      Env

      OCP 4.10.0-fc.2
      Kata operator v1.1.0
      Node: 80 CPU (Intel Xeon Gold 6248), 128GiB RAM

      Additional helpful info

      See attached.

      Attachments

        1. mssql.yaml
          2 kB
          Robert Krawitz
        2. mssql-annotation.yaml
          5 kB
          Robert Krawitz
        3. mssql-deployment-69b9577b8-5cmsn
          3 kB
          Robert Krawitz

        Activity

          People

            Unassigned Unassigned
            robertkrawitz Robert Krawitz
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated: