Description of problem: when user tries to use the same mount point to mount the brick it gives Unexpected Exception. Instead of exception UI should display a message saying this mount point is being used. Version-Release number of selected component (if applicable): ovirt-engine-webadmin-portal-3.6.0-0.0.master.20150406175153.gite240701.el6.noarch How reproducible: Always Steps to Reproduce: 1. Create a brick and mount it in /gluster-bricks/b3. 2. Now try creating another brick and give the same brick name 3. Actual results: Operation gets cancelled by displaying an unexpected exception. Expected results: UI should display proper message saying the mount point is already in use/ brick name is already in use. Additional info:
Engine logs can be found in the link below. http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1209475/
Also please attach the node logs
Logs are attached in the link present in comment 1
Path sent to upstream for review: https://bugzilla.redhat.com/show_bug.cgi?id=1209475
Patch url: https://gerrit.ovirt.org/#/c/40892/
Moving this bug to assigned because engine still gives Unexpected Exception.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high
This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset. Please set the correct milestone or add the flag.
Sorry for the noise with assignee. something went wrong while setting target release. Yaniv, why did you changed TR to 3.6.2.1? last patch is from 2015-12-30 which is post 3.6.2.1 release
(In reply to Sandro Bonazzola from comment #11) > Sorry for the noise with assignee. something went wrong while setting target > release. > > Yaniv, why did you changed TR to 3.6.2.1? last patch is from 2015-12-30 > which is post 3.6.2.1 release The 3.6.2 patch is included in tag ovirt-engine-3.6.2.1.
Tested with RHEV 3.6.2.6 and RHGS Nightly ( glusterfs-3.7.5-17.el7rhgs ) when user tries to use the same mount point to mount the brick, UI displays a proper error message which reads "Error while executing Create Brick: Mount Point is in use'