All handlers succeeded for creation despite raising kopf.HandlerFatalError about kopf HOT 3 CLOSED

Thanks for reporting.

It seems like improper phrasing in the logs. The logic is as intended.

kopf.PermanentError (aliased as legacy kopf.HandlerFatalError) tells the framework to give up on this specific handler, and never retry it again. Once it is raised —assuming it is the only handler— there are no more handlers to try either now or later, including this same failed handler's retries, and so the handling cycle ends.

This is marked by a phrase "all handlers succeeded" meaning that "all handlers have been tried and all of them have done what they could and I have nothing to do and bye-bye". This is the opposite to the case when there are handlers left to try/retry later until this handling cycle is finished.

A "handling cycle" is an internal term for full processing of a single cause (creation, update, deletion) with all matching handlers. I'm not sure if the "handling cycle" term should be exposed to the user.

I would be happy if you suggest a better phrasing that makes it more clear and less confusing.

from kopf.

Supposing the response is not conditional I think it is slightly better phrasing to simply say: All handlers finished for creation or All handlers completed for creation. Or since not 'all' handlers may be run, just drop the 'all'.

But I do think it should have conditional phrasing. I think omission works since there is a previous message that says what failed. If an explicit message is still wanted though, maybe: Handlers for creation aborted

from kopf.

Solved nolar/kopf#540, available since kopf>=0.28rc2

from kopf.