Description of problem: When user tries to remove a brick with out migrating data on them, brick does not get removed from the volume and it gets added as a new brick to the volume and data migration on that brick starts. Version-Release number of selected component (if applicable): ovirt-engine-webadmin-portal-3.6.0-0.0.master.20150105124153.git669ddc1.el6.noarch How reproducible: Always Steps to Reproduce: 1. Create a volume of type distribute. 2. Click on the bricks sub tab. 3. select one brick from the volume and click remove. 4. In the remove brick dialog box uncheck "Migrate data from bricks". Actual results: Brick gets removed from the volume and gets added as a new brick. Data migration starts on that brick. Expected results: Brick should be removed from the volume. Data migration should not be started on that brick as migrate data from bricks option is unchecked. Additional info:
Please attach logs
please find the logs in the link provided below. Attaching engine and vdsm logs. http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1184370/
This issue is seen only in json-rpc mode. Mostly engine is not invoking the proper vdsm verb in json rpc mode. It has to invoke GlusterVolume.removeBrickForce() when brick is to be removed without data migration.
You are right Darshan this is because when JsonRpcVdsServer was added it missed the conditional handling of a force and non-force remove bricks. However, I find that in xml-rpc mode, the remove brick is handled conditionally appropriately.
Verified the fix on build ovirt-engine-3.6.0-0.0.master.20150518173633.gitcf0f078.el6.noarch It works fine in json-rpc mode.
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one.