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

kataconfig shows runtimeClass as kata when enablePeerPods = true

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • OSC 1.5.0
    • OSC 1.4.0
    • Operator
    • None
    • False
    • None
    • False
    • Hide
      Previously, when you enabled peer pods in the `KataConfig` CR and then examined the CR after installation, the `kata-remote` runtime class was not displayed in the `status.runtimeClass` field. This is fixed in {sandboxed-containers-first} 1.5.0. (link:https://issues.redhat.com/browse/KATA-2164[*KATA-2164*])
      Show
      Previously, when you enabled peer pods in the `KataConfig` CR and then examined the CR after installation, the `kata-remote` runtime class was not displayed in the `status.runtimeClass` field. This is fixed in {sandboxed-containers-first} 1.5.0. (link: https://issues.redhat.com/browse/KATA-2164 [* KATA-2164 *])
    • Bug Fix
    • Done
    • 0
    • 0

      Description

      oc get kataconfig example-kataconfig -n openshift-sandboxed-containers-operator -o yaml

       shows the wrong runtimeClass when running peerpods

      Steps to reproduce

      <What actions did you take to hit the bug?>
      1. install kataconfig with   enablePeerPods: true
      2. watch oc get kataconfig example-kataconfig -n openshift-sandboxed-containers-operator -o yaml 
      3. wait as kataconfig finishes install

      Expected result

      Initially, runtimeClass: ""
       Changes to runtimeClass: kata-remote-cc

      Actual result

      apiVersion: kataconfiguration.openshift.io/v1
kind: KataConfig
metadata:
  creationTimestamp: "2023-05-11T14:24:02Z"
  finalizers:
  - kataconfiguration.openshift.io/finalizer
  generation: 2
  name: example-kataconfig
  resourceVersion: "76926"
  uid: 2aec57dc-b30e-41c3-819a-a66a8de68ba6
spec:
  checkNodeEligibility: false
  enablePeerPods: true
  kataConfigPoolSelector: null
  logLevel: info
status:
  installationStatus:
    IsInProgress: "False"
    completed:   
      completedNodesCount: 3
      completedNodesList:
      - tbuskey-230511-1-92rcq-worker-eastus1-z9fns
      - tbuskey-230511-1-92rcq-worker-eastus2-94ldg
      - tbuskey-230511-1-92rcq-worker-eastus3-9htv7
    failed: {}                 
    inprogress: {}             
  runtimeClass: kata
  totalNodesCount: 3
  unInstallationStatus:
    completed: {}
    failed: {}
    inProgress:
      status: ""
  upgradeStatus: {}
  waitingForMcoToStart: false

       

      Impact

      <How badly does this interfere with using the software?>

      Env

      OCP 4.13-rc8

      OSC 1.4.0-115, 117

      Additional helpful info

       

      oc get runtimeclass
NAME             HANDLER          AGE
kata             kata             18m
kata-remote-cc   kata-remote-cc   18m

              Unassigned Unassigned
              tbuskey-rh Tom Buskey
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: