Bug 1040202 - rest api: incorrect error message when activating bricks after migration has finished and volume is down
Summary: rest api: incorrect error message when activating bricks after migration has ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc-sdk
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Shubhendu Tripathi
QA Contact: Mike McCune
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-10 22:41 UTC by Dustin Tsang
Modified: 2015-09-01 13:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-01 13:30:20 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dustin Tsang 2013-12-10 22:41:18 UTC
Description of problem:

Incorrect error message when activating bricks when migration has finished and brick is down

"Cannot stop remove bricks Gluster Brick. Gluster Volume should be started."

User is not stopping or removing any Gluster Bricks.

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


How reproducible:
rhsc-cb10

Steps to Reproduce:
1. create a volume in rhsc
2. via rest api, migrate 2 bricks from volume
3. wait until migration has finished
4. stop the volume
5. activate the bricks that were migrated
--------------- sample request ------
2013-12-10 17:29:12,636 [main] DEBUG org.apache.http.headers - >> POST /api/clusters/5486f353-454e-45d8-a3d8-368b7968148d/glustervolumes/82925311-55d8-4742-805c-8c327e34d903/bricks/activate HTTP/1.1
2013-12-10 17:29:12,636 [main] DEBUG org.apache.http.headers - >> Content-Type: application/xml
2013-12-10 17:29:12,636 [main] DEBUG org.apache.http.headers - >> Accept: application/xml
2013-12-10 17:29:12,637 [main] DEBUG org.apache.http.headers - >> Content-Length: 301
2013-12-10 17:29:12,637 [main] DEBUG org.apache.http.headers - >> Host: latest.rhsc:443
2013-12-10 17:29:12,637 [main] DEBUG org.apache.http.headers - >> Connection: Keep-Alive
2013-12-10 17:29:12,637 [main] DEBUG org.apache.http.headers - >> User-Agent: Apache-HttpClient/4.1.3 (java 1.5)
2013-12-10 17:29:12,637 [main] DEBUG org.apache.http.headers - >> Authorization: Basic YWRtaW5AaW50ZXJuYWw6cmVkaGF0
2013-12-10 17:29:12,637 [main] DEBUG org.apache.http.wire - >> "<?xml version="1.0" encoding="UTF-8" standalone="yes"?>[\n]"
2013-12-10 17:29:12,637 [main] DEBUG org.apache.http.wire - >> "<action>[\n]"
2013-12-10 17:29:12,637 [main] DEBUG org.apache.http.wire - >> "    <bricks>[\n]"
2013-12-10 17:29:12,637 [main] DEBUG org.apache.http.wire - >> "        <brick>[\n]"
2013-12-10 17:29:12,638 [main] DEBUG org.apache.http.wire - >> "            <name>latest-a:/tmp/201312101727230641942637805</name>[\n]"
2013-12-10 17:29:12,638 [main] DEBUG org.apache.http.wire - >> "        </brick>[\n]"
2013-12-10 17:29:12,638 [main] DEBUG org.apache.http.wire - >> "        <brick>[\n]"
2013-12-10 17:29:12,638 [main] DEBUG org.apache.http.wire - >> "            <name>latest-b:/tmp/20131210172723630850249563</name>[\n]"
2013-12-10 17:29:12,638 [main] DEBUG org.apache.http.wire - >> "        </brick>[\n]"
2013-12-10 17:29:12,638 [main] DEBUG org.apache.http.wire - >> "    </bricks>[\n]"
2013-12-10 17:29:12,638 [main] DEBUG org.apache.http.wire - >> "</action>[\n]"
=------------

Actual results:
Http 409 received with reason
"Cannot stop remove bricks Gluster Brick. Gluster Volume should be started."

Expected results:
Something similar to
"Cannot activate bricks. Gluster volume is down"

Additional info:

Comment 2 Dusmant 2013-12-16 08:51:02 UTC
Not taking it up for Corbett

Comment 5 Dusmant 2015-09-01 13:30:20 UTC
We are not planning to address this new feature. Hence closing this BZ. If you think, it's applicable for 3.x or beyond release and would have an impact on customer, pls. open up a new BZ with the appropriate version. Thanks, -Dusmant

Comment 6 Dusmant 2015-09-01 13:51:09 UTC
Slight correction to Comment 5 :

We are not planning to fix it. Hence closing this BZ. If you think, it's applicable for 3.x release and would have an impact on customer, pls. open up a new BZ with the appropriate version. Thanks, -Dusmant


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