In the management API client, when calling getJobStatus, we have noticed that the status can be COMPLETE, but the statusChanges field can be completely null.
This causes downstream null pointer exceptions in Reaper and does not make sense (since we assume that the repair must have been running at some point to reach COMPLETE).
Definition of done
We always get at least the latest status change back from Management API.
In the management API client, when calling
getJobStatus
, we have noticed that the status can be COMPLETE, but the statusChanges field can be completely null.This causes downstream null pointer exceptions in Reaper and does not make sense (since we assume that the repair must have been running at some point to reach COMPLETE).
Definition of done
We always get at least the latest status change back from Management API.
┆Issue is synchronized with this Jira Story by Unito