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

OSC operator upgrade doesn't update CRI-O and Kata config files

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: High High
    • OSC 1.7.0
    • OSC 1.7.0
    • Operator
    • None
    • False
    • None
    • False
    • Kata Sprint #258
    • 0
    • 0

      Description

      Upgrade from OSC 1.6.0 to 1.7.0 doesn't update CRI-O and Kata config files.

      Steps to reproduce

      1. Deploy OSC 1.6.0
      2. Create KataConfig for peer pods
      3. Upgrade to OSC 1.7.0
      4. oc debug -q node/${KATA_ENABLED_NODE} -- cat /host/etc/crio/crio.conf.d/50-kata-remote

      Expected result

      [crio.runtime.runtimes.kata]
  runtime_path = "/usr/bin/containerd-shim-kata-v2"
  runtime_type = "vm"
  runtime_root = "/run/vc"
  privileged_without_host_devices = true

      Actual result

      [crio.runtime.runtimes.kata]
  runtime_path = "/usr/bin/containerd-shim-kata-v2-tp"
  runtime_type = "vm"
  runtime_root = "/run/vc"
  privileged_without_host_devices = true

      Impact

      Peer pods GA feature doesn't work after upgrade to 1.7.

      Env

      OCP 4.14 on ARO

      Additional helpful info

            rhgkurz Greg Kurz
            rhgkurz Greg Kurz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: