Node Health Attribute (-1000000) Not Automatically Reset After Critical Failure in Resource-Agent Update

[rnirek]

We have observed that with the recent update to the resource-agent configuration, as outlined in Cluster Lab resource-agents, once a node is marked with a value of -1000000—indicating a critical failure or an unhealthy state—the attribute remains unchanged until it is manually modified. Consequently, cluster services will not restart until this manual intervention occurs.

Could you clarify the rationale behind why the value is not automatically reset to 0?