Red Hat Bugzilla – Bug 988094
[ExternalTasks] Cannot end existing job
Last modified: 2013-09-23 03:28:09 EDT
Assume JOB_ID is ID of existing job.
Assume USER_ID is ID of existing user.
POST response = fault
<detail>[action type non monitored]</detail>
GET /api/jobs/JOB_ID = job is still in STARTED state, POST request doesn't seem to have any effect
<job href="/api/jobs/JOB_ID" id="JOB_ID">
<link href="/api/jobs/JOB_ID/clear" rel="clear"/>
<link href="/api/jobs/JOB_ID/end" rel="end"/>
<owner href="/api/users/USER_ID" id="USER_ID"/>
Please advise what is the proper way to end a job with given state.
Is this the case were
1) All steps under the job were successfully ended manually
2) Then the job is attempted to end
(In reply to Eli Mesika from comment #1)
> Is this the case were
> 1) All steps under the job were successfully ended manually
> 2) Then the job is attempted to end
Yes, exactly. All steps under the given job were ended using succeeded=true because succeeded=false didn't work when trying to end a step (see https://bugzilla.redhat.com/988088).
So if all steps were ended as successful, the corresponding job will also be ended as successful? In other words, when ending a job, the status is calculated depending on status of all its steps?
fixed in commit : 0052968
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)