Description of problem: After stop or retain of the remove brick task start removing a different brick from the same volume. Status window cannot be opened on GUI, it always print: Could not fetch remove brick status of volume : <volume_name> Version-Release number of selected component (if applicable): rhsc-3.1.0-0.60 How reproducible: 100% Steps to Reproduce: 1. Have a volume with at least two bricks 2. Start to remove brick 3. Stop or retain the remove brick task 4. Start to remove some other brick 5. Try to open status window on GUI Actual results: Status window cannot be opened Could not fetch remove brick status of volume : <volume_name> Expected results: Status is displayed correctly Additional info: Migrate data are always checked. Remove brick task could be initiated from CLI.
Please attach engine logs
Engine logs: http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1234445/sosreport-LogCollector-20150629132659.tar.xz
I tried opening the logs attached but looks like I don't have the required permissions. Please check if the remove brick status gluster command with "--xml" returns the status correctly. If the command with the "--xml" doesn't return anything then this is the expected behavior from RHGSC
(In reply to anmol babu from comment #3) > I tried opening the logs attached but looks like I don't have the required > permissions. Please check if the remove brick status gluster command with > "--xml" returns the status correctly. If the command with the "--xml" > doesn't return anything then this is the expected behavior from RHGSC It works fine: # gluster volume remove-brick dis-vol <IP>:/rhgs/brick3/brick3 status --xml <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <cliOutput> <opRet>0</opRet> <opErrno>0</opErrno> <opErrstr/> <volRemoveBrick> <task-id>c990b0d6-9912-4815-873e-9cbefe66822c</task-id> <nodeCount>4</nodeCount> <node> <nodeName>IP</nodeName> <id>272d26a1-0f96-46b6-9aa4-7fec13b62ebb</id> <files>4</files> <size>2097152000</size> <lookups>20</lookups> <failures>0</failures> <skipped>0</skipped> <status>1</status> <statusStr>in progress</statusStr> <runtime>51.00</runtime> </node> <aggregate> <files>4</files> <size>2097152000</size> <lookups>20</lookups> <failures>0</failures> <skipped>0</skipped> <status>1</status> <statusStr>in progress</statusStr> <runtime>51.00</runtime> </aggregate> </volRemoveBrick> </cliOutput>
Doc text is edited. Please sign off to be included in Known Issues.
Looks good
Could be an issue with the query formed. Need to check.
Thank you for your report. This bug is filed against a component for which no further new development is being undertaken