Description:
In mto code, if the ENOExecEvent status update fails, it will trigger rollbackFn , Since rollbackFn may inevitably fail during execution and it only logs errors when deletion fails, and because the controller skips EnoExecEvent if it's .status.podName=="" , this could leave orphaned CRs in the cluster.

The influence:

Leaving orphaned CRs can block the deletion of ClusterPodPlacementConfig.

Workaround:

Manually delete ENOExecEvent CRs in the operator namespace if ClusterPodPlacementConfig deletion is blocked.