-
Bug
-
Resolution: Done
-
Medium
-
None
-
OSC 1.4.1, OSC 1.5.0
-
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
- Create an OCP 4.14 cluster
- Install OSC 1.5.0-11
- Deploy kata
- Start a pod using the kata runtime
- Delete the KataConfig CR
- Wait for "Kata PODs are present. Requeue for reconciliation" in the operator log
- Delete the pod
- 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
- links to
- mentioned on
(1 mentioned on)