Hide Forgot
Description of problem: The status of job for migrating a set of bricks always reports STARTED. Also the executing step for the job also remains in he STARTED state even though its children's state are FINISHED. Version-Release number of selected component (if applicable): rhsc-cb10 How reproducible: 100% of the time Steps to Reproduce: 1. create a dist volume in rhsc 2. using the rest api migrate 2 bricks => job id is returned 3. using the gluster cli monitor the migration status by running 'gluster vol status' 4. when migration has complete, use the rest api to show the job (GET /api/jobs/:id ) Actual results: The status of the job is STARTED Expected results: The status of the job should be FINISHED Additional info:
As per Dustin, the REST API shows "STARTED" but on the GUI it shows "FINISHED".
Dustin/Dusmant, In engine we keep the status of remove brick as STARTED till user performs stop/commit. So REST would keep showing as STARTED only and user should either execute delete action to remove the brick or activate action to retain the brick. It is done this way to make sure user gets an alert that after migrate he has to perform either delete or retain. Actually in UI we keep showing an icon with "?" overlapped with remove brick icon just to indicate that migrate is completed but either delete or activate should be executed to complete the task. Till then the task in engine would be marked as STARTED only. Hope this clarifies.
Then, in this case it would not be considered as a bug. I will close this bug. But we need to document this API behaviour in the API guide.