Slack thread https://redhat-internal.slack.com/archives/C03M5GKJNBA/p1771084985337179 raises the discussion of unreachable code that checks if ErrorOnLeaseCount has exceeded maxAllowedErrorToUpdateOwnedLease, and then it will uncordon the node and report maintenance has failed.

This whole behavior doesn't work, since NMO doesn't change the ErrorOnLeaseCount value.