Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1053112 - stopMigrate does not stop migration immediately
stopMigrate does not stop migration immediately
Status: CLOSED EOL
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc-sdk (Show other bugs)
2.1
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Shubhendu Tripathi
Mike McCune
:
Depends On:
Blocks: 1035040
  Show dependency treegraph
 
Reported: 2014-01-14 12:20 EST by Dustin Tsang
Modified: 2015-12-03 12:21 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
When large sized files are migrated, the stop migrate task does not stop the migration immediately but only after the migration is completed.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-12-03 12:21:40 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dustin Tsang 2014-01-14 12:20:06 EST
Description of problem:

Stop migrate does not stop migration immediately. This is a problem when the client is trying to perform operations on volume after stopMigrate is called.


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

How reproducible:
90% of the time


Steps to Reproduce:
1.create a volume and start the volume
2.create some data on volume so that each brick has data
3.migrate a few bricks
4.via api, call stop migrate on the volume
5.immediately after, call stop volume

Actual results:
400 response
2014-01-10 17:10:41,038 [main] DEBUG org.apache.http.wire - << "<?xml version="1.0" encoding="UTF-8" standalone="yes"?>[\n]"¬
2014-01-10 17:10:41,038 [main] DEBUG org.apache.http.wire - << "<action>[\n]"¬
2014-01-10 17:10:41,038 [main] DEBUG org.apache.http.wire - << "    <status>[\n]"¬
2014-01-10 17:10:41,038 [main] DEBUG org.apache.http.wire - << "        <state>failed</state>[\n]"¬
2014-01-10 17:10:41,038 [main] DEBUG org.apache.http.wire - << "    </status>[\n]"¬
2014-01-10 17:10:41,038 [main] DEBUG org.apache.http.wire - << "    <fault>[\n]"¬
2014-01-10 17:10:41,038 [main] DEBUG org.apache.http.wire - << "        <reason>Operation Failed</reason>[\n]"¬
2014-01-10 17:10:41,038 [main] DEBUG org.apache.http.wire - << "        <detail>[volume stop failed[\n]"¬
2014-01-10 17:10:41,039 [main] DEBUG org.apache.http.wire - << "error: rebalance session is in progress for the volume 'startnegativerepcount'[\n]"¬
2014-01-10 17:10:41,039 [main] DEBUG org.apache.http.wire - << "return code: -1]</detail>[\n]"¬
2014-01-10 17:10:41,039 [main] DEBUG org.apache.http.wire - << "    </fault>[\n]"¬
2014-01-10 17:10:41,039 [main] DEBUG org.apache.http.wire - << "</action>[\n]"¬

Expected results:

stop volume succeeds every time.


Additional info:
Comment 2 Shalaka 2014-01-29 01:11:20 EST
Please review the edited Doc Text and sign off.
Comment 3 Shubhendu Tripathi 2014-01-29 01:24:56 EST
doc text looks fine
Comment 6 Vivek Agarwal 2015-12-03 12:21:40 EST
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/

If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.

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