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

Build 1.5.0-11 can hit the "object has been modified" error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • OSC 1.4.1, OSC 1.5.0
    • Operator
    • None
    • 8
    • False
    • None
    • False
    • 0
    • 0.000

      Description

      The k8s server can block the removal of the finalizer on the KataConfig, especially if the user tries to delete the KataConfig while at least one POD is using the kata runtime.

      Steps to reproduce

      1. Create an OCP 4.14 cluster
      2. Install OSC 1.5.0-11
      3. Deploy kata
      4. Start a pod using the kata runtime
      5. Delete the KataConfig CR
      6. Wait for "Kata PODs are present. Requeue for reconciliation" in the operator log
      7. Delete the pod
      8. Watch the operator log

      Expected result

      INFO    controllers.KataConfig  Removing finalizer from the KataConfig
      INFO    controllers.KataConfig  Reconciling KataConfig in OpenShift Cluster
      

      Actual result

      INFO    controllers.KataConfig  Removing finalizer from the KataConfig
      ERROR   controllers.KataConfig  Unable to update KataConfig     {"error": "Operation cannot be fulfilled on kataconfigs.kataconfiguration.openshift.io \"example-kataconfig\": the object has been modified; please apply your changes to the latest version and try again"}
      

      Impact

      This is likely to cause the operator to hit KATA-1213 (never ending reconcile loop).

      Env

      Additional helpful info

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

                Created:
                Updated:
                Resolved: