In rare cases, some jobs that show a successful status in the Jobs summary page in the Resources area, report a failed job status on the individual Job's Details tab, even though the status icon shows a green status. For example, the following figure shows a job with a green status icon, but a failure error.

Figure 6-1 Incorrect Status

This discrepancy in status is caused by the system job reaper running before the task completes and does not actually indicate that the job has failed. You can safely ignore these failure messages after verifying the job status shows that it has a Successful status on the Jobs page and shows a green status icon on the Details tab of the individual job. You can also verify the status of the job using the /api/v2/jobs/ API call.

Resolved: This issue has been resolved in Oracle Linux Automation Manager release 2.1. Use the REAPER_TIMEOUT_SEC parameter to adjust the duration before the reaper timeout occurs. This prevents the reaper from changing the status of long running jobs to failed. For more information about the REAPER_TIMEOUT_SEC parameter, see the Oracle Linux Automation Manager 2.1: Installation Guide.