Ansible operator markDone function causing DPANIC in reconcile.go #2025
Labels
kind/bug
Categorizes issue or PR as related to a bug.
language/ansible
Issue is related to an Ansible operator project
Bug Report
When deleting a CR , markDone function is causing DPANIC
What did you do?
Deleting CR is causing above issue
What did you expect to see?
markDone call should not cause DPANIC when it cannot find the Kubernetes object
What did you see instead? Under which circumstances?
During CR deletion, markDone function call is causing DPANIC
Environment
operator-sdk version: v0.10.x,
go version: go1.12.4
Kubernetes version information: v1.11.0+d4cacc0
Kubernetes cluster kind: Openshift v3.11.141
Are you writing your operator in ansible, helm, or go?
Ansible
Possible Solution
Don not pass the 'err' object to the logger call below
logger.Info("Resource not found, assuming it was deleted", err)
The text was updated successfully, but these errors were encountered: