Bug 558569 - the Samba Share "Resource Name:" parameter not being used anywhere
Summary: the Samba Share "Resource Name:" parameter not being used anywhere
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: RHQ Project
Classification: Other
Component: Configuration
Version: 1.4
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: RHQ_Config
TreeView+ depends on / blocked
 
Reported: 2010-01-25 17:29 UTC by John Sefler
Modified: 2014-05-23 21:01 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-23 21:01:15 UTC
Embargoed:


Attachments (Terms of Use)

Description John Sefler 2010-01-25 17:29:14 UTC
Description of problem:
When creating a Samba Share child resource within the iManage UI, there are two paramters whose usage is confusing:
1. Resource Name:
2. Name

The "Name" parameter is used to actually name the share.  It gets written to the smb.conf file as the share name.  It is used as the Resource Key for the child resource.  And it is appended by the string " share" to identify the share as a child resource of the Samba Server.

So the problem is:
Where does the "Resource Name:" value get used?  It looks like nowhere.

Expected results:
Personally I believe the intended design was for the "Resource Name:" value was to be used to name the child resource in the UI.  Therefore the hard-coded appending of " share" to the Name value is a bug.  The samba shares (child resources) of a samba server should be presented in the UI by the "Resource Name:" values entered at creation time.

Comment 1 wes hayutin 2010-02-16 16:53:58 UTC
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug

Comment 2 wes hayutin 2010-02-16 16:59:16 UTC
making sure we're not missing any bugs in rhq_triage

Comment 3 Corey Welton 2010-09-30 14:09:12 UTC
lowering severity/priority - not an enterprise plugin


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