Bug 1033973 - REST: remove brick job does not report finished state even though job has finished
Summary: REST: remove brick job does not report finished state even though job has fin...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc-sdk
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Shubhendu Tripathi
QA Contact: Dustin Tsang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-24 22:15 UTC by Dustin Tsang
Modified: 2015-07-13 04:39 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-25 09:06:15 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Dustin Tsang 2013-11-24 22:15:12 UTC 
Description of problem:

The remove-brick job reports status as STARTED when gluster remove-brick has finished. In rhsc gui/gluster cli, shows that all remove-brick operation has completed. Job should report FINISHEd when remove-brick job has finished.


Version-Release number of selected component (if applicable):
rhsc-cb8

How reproducible:
100%

Steps to Reproduce:
1. setup a 2 node cluster
2. create a dist volume
3. via rest api call the migrate operation on 2 bricks
4. using the gluster-cli, wait for `gluster volume status` command to report job has finished.
5. perform a show on the job (GET on the /api/job/:id)

Actual results:
the status shown in the response is STARTED


Expected results:
the status show should be FINISHED


Additional info:
Comment 2 Dusmant 2013-11-25 09:06:15 UTC 
You should commit to see the job status has finished or not.
Note You need to log in before you can comment on or make changes to this bug.