Bug 988088 - [ExternalTasks] Step cannot be ended as not successful
Summary: [ExternalTasks] Step cannot be ended as not successful
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Eli Mesika
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-24 17:36 UTC by Vojtech Szocs
Modified: 2013-09-23 07:27 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-23 07:27:19 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 17463 0 None None None Never

Description Vojtech Szocs 2013-07-24 17:36:49 UTC
Assume JOB_ID is ID of existing job.
Assume STEP_ID is ID of existing step that belongs to above mentioned job.

POST /api/jobs/JOB_ID/steps/STEP_ID/end
<action>
  <succeeded>false</succeeded>
</action>

GET /api/jobs/JOB_ID/steps/STEP_ID = step is still in STARTED state, POST request doesn't seem to have any effect
<step href="/api/jobs/JOB_ID/steps/STEP_ID" id="STEP_ID">
    <actions>
        <link href="/api/jobs/JOB_ID/steps/STEP_ID/end" rel="end"/>
    </actions>
    <description>Test Step</description>
    <job href="/api/jobs/JOB_ID" id="JOB_ID"/>
    <type>executing</type>
    <number>0</number>
    <status>
        <state>STARTED</state>
    </status>
    <start_time>2013-07-24T16:52:36.943+02:00</start_time>
    <external>true</external>
</step>

Please advise what is the proper way to end a step so that its state is something other than FINISHED.

Comment 1 Eli Mesika 2013-08-01 11:18:29 UTC
fixed in commit : d849805

Comment 2 Itamar Heim 2013-08-21 16:41:48 UTC
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)

Comment 3 Itamar Heim 2013-09-23 07:27:19 UTC
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)


Note You need to log in before you can comment on or make changes to this bug.