Bug 1258038 - [New] - UI generates unexpected exception when user tries to create a brick with existing brick name.
Summary: [New] - UI generates unexpected exception when user tries to create a brick w...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: RHS-C QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-28 17:57 UTC by RamaKasturi
Modified: 2023-09-14 03:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-29 15:13:35 UTC
Embargoed:


Attachments (Terms of Use)

Description RamaKasturi 2015-08-28 17:57:37 UTC
Description of problem:
When user tries to create a brick using the same brick name which already exists and with a different mount point gives unexpected exception.

Unexpected exception gets displayed when UI fails to sync storage devices as well.

Version-Release number of selected component (if applicable):
rhsc-3.1.1-0.64.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a brick with name brick1 and mount it under /rhgs/brick1
2. Now try creating another brick by providing the same brick name with different mount point.
3. Try syncing the storage devices and make sure that a failure happens.

Actual results:
UI displays unexpected exception in both the above cases mentioned in the description.

Expected results:
UI should display a proper message when brick name is given as the one which already exists and when UI fails to sync storage devices.

Additional info:

Comment 3 Sahina Bose 2016-03-23 06:19:46 UTC
Can you move to ON_QA if this has been fixed?

Comment 6 Sahina Bose 2018-01-29 15:13:35 UTC
Thank you for your report. This bug is filed against a component for which no further new development is being undertaken

Comment 7 Red Hat Bugzilla 2023-09-14 03:04:25 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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