cr deletion not happening

[malli31]

Bug Report

What did you do?

Install operator
install CR
try to delete CR
its always in waiting state

What did you expect to see?

Want CR deletion to complete

What did you see instead? Under which circumstances?

Its always in waiting state and seeing below reconsile error
{"level":"error","ts":1671773874.4158955,"msg":"Reconciler error","controller":"universalmonitoringagent-controller","object":{"name":"uma-monitor","namespace":"caapm"},"namespace":"caapm","name":"uma-monitor","reconcileID":"35679e74-c88e-4412-9d77-e2519525c21f","error":"failed to delete release: uma-monitor","errorVerbose":"failed to delete release: uma-monitor\nhelm.sh/helm/v3/pkg/action.(*Uninstall).Run\n\t/go/pkg/mod/helm.sh/helm/[email protected]/pkg/action/uninstall.go:118\ngithub.com/operator-framework/operator-sdk/internal/helm/release.manager.UninstallRelease\n\t/workspace/internal/helm/release/manager.go:372\ngithub.com/operator-framework/operator-sdk/internal/helm/controller.HelmOperatorReconciler.Reconcile\n\t/workspace/internal/helm/controller/reconcile.go:125\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:121\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:320\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:273\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:234\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1594","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:326\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:273\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:234"}

Environment

BOTH KUBERNETES 1.25 OR OPNEHSHIFT 4.11
Operator type:
Helm Operator

Kubernetes cluster type:
Multinode

$ operator-sdk version

$ go version (if language is Go)

$ kubectl version

Possible Solution

Additional context

[malli31]

Especially seeing this error with helm sdk upgraded to 1.25.3 or 1.26.0
everything working perfect with 1.22.x

[malli31]

in operator pod seeing below error followed by error mentioned earlier
{"level":"info","ts":1671787659.7043393,"logger":"helm.controller","msg":"Upgraded release","namespace":"caapm","name":"uma-monitor","apiVersion":"ca.broadcom.com/v1alpha1","kind":"UniversalMonitoringAgent","release":"uma-monitor","force":false}
{"level":"error","ts":1671787660.0682108,"msg":"Reconciler error","controller":"universalmonitoringagent-controller","object":{"name":"uma-monitor","namespace":"caapm"},"namespace":"caapm","name":"uma-monitor","reconcileID":"5601109c-f696-4294-8897-cc168623c857","error":"Operation cannot be fulfilled on universalmonitoringagents.ca.broadcom.com "uma-monitor": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:326\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:273\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:234"}

[malli31]

@varshaprasad96 @laxmikantbpandhare any update on this plz

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.