You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rayServiceLog.Error(err, "Fail to update status of RayService", "rayServiceInstance", rayServiceInstance)
return ctrl.Result{}, err
}
But if we do explicitly log the errStatus message, under one failure condition, it will say:
"error": "Operation cannot be fulfilled on rayservices.ray.io \"rayservice-sample\": the object has been modified; please apply your changes to the latest version and try again", "error": "Operation cannot be fulfilled on rayservices.ray.io \"rayservice-sample\": the object has been modified; please apply your changes to the latest version and try again"}
Steps to repro:
create the sample rayservice
kubectl delete pod HEAD_POD
tail the controller logs
The text was updated successfully, but these errors were encountered:
Thanks for finding the typo issue. Will fix it soon.
The second issue is quite common, it is due to the resource version of the CR changes, and it will try another reconcile loop.
It is a normal case.
If we do a very simple reconcile loop:
Read a CR, update state, Update the CR. I think the issue still there. It should be a common case in k8s.
If you have more insights or find out we update CR twice in the loop, that could fix the issue!
First of all, this error handling block is broken, the logger should log
errStatus
instead of the globalerr
.kuberay/ray-operator/controllers/ray/rayservice_controller.go
Lines 193 to 196 in 68faa10
But if we do explicitly log the
errStatus
message, under one failure condition, it will say:Steps to repro:
kubectl delete pod HEAD_POD
The text was updated successfully, but these errors were encountered: