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

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

      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.

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

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

              Created:
              Updated: