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

kata-containers 3.13 and 3.17 doesn't work on OCP 4.19

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: High High
    • None
    • OSC 1.10.0
    • kata-containers
    • None
    • Quality / Stability / Reliability
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Kata Sprint #270, Kata Sprint #271
    • 0

      Description

      While smoke testing theĀ kata-containers-3.17.0-1.rhaos4.19.el9_6.x86_64 scratch RPM, a sandboxed container won't start on OCP 4.19.

      Steps to reproduce

      <What actions did you take to hit the bug?>
      1. Install OSC 1.9 on OCP 4.19
      2. Create KataConfig
      3. Unlock ostree and upgrade kata-containers
      4. Start a simple kata pod

      Expected result

      Pod starts.

      Actual result

      Pod fails to start :

      oc describe pod
      ...
      Events:
        Type     Reason                  Age                From               Message
        ----     ------                  ----               ----               -------
        Normal   Scheduled               5m45s              default-scheduler  Successfully assigned groug/example-fedora-kata to greg3-worker-0.ocp-groug.com
        Normal   AddedInterface          13s (x2 over 20s)  multus             Add eth0 [10.133.2.34/23] from ovn-kubernetes
        Warning  FailedCreatePodSandBox  7s (x2 over 14s)   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = CreateContainer failed: ttrpc: closed: unknown
      

      Impact

      OSC 1.10 won't be able to run non-peerpods sandboxed containers on OCP 4.19.

      Env

      OCP 4.19.0
      OSC 1.9.0
      kata-containers 3.17.0

      Additional helpful info

              rhgkurz Greg Kurz
              rhgkurz Greg Kurz
              John Wilkins John Wilkins
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: