Details
-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
Description
As I have already discussed with swiderski.maciej, there is a bug which causes that SLA is not properly updated for the correct node in DB after it is violated. This is because currently query updates row with matching nodeInstanceId, but it is not unique across all processes, only per process. It should use both processInstanceId and nodeInstanceId to correctly find the desired NodeInstanceLog row.
Attachments
Issue Links
- clones
-
RHPAM-1023 Node SLA is not updated for the right node
- Closed