Description of problem: When creating a Samba share through iManage, an unexpected parameter is being set within the share's section name. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Create a Samba share through the iManage UI. Set the following UI fields: Resource Name: testResourceName Name: testName Path: /tmp/testNameShare click Submit 2. On the agent's filesystem: cat /etc/samba/smb.cnf Notice the newly added samba section [testName]. The "name = testName" parameter is superfluous and unrecognised by samba's own testparm configuration checking tool. Actual results: [testName] name = testName path = /tmp/testNameShare Expected results: [testName] path = /tmp/testNameShare Additional info: Try running on the command line: testparm -sv --section-name=testName Processing section "[testName]" Unknown parameter encountered: "name" Ignoring unknown parameter "name" Loaded services file OK. [testName] path = /tmp/testNameShare
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
ps -- can we do semantic validation when a config is saved?
s/ps/ips/ -- that question was directed at you, ian :)
Corey, yes, when the user clicks the Save button, updateConfiguration() is called on the plugin, and if the plugin finds issues with certain property values, it can set validation error messages on those properties and then send back a failed response to the Server, which includes the property-specific errors. The GUI will then display the property-specific errors next to the corresponding properties.
Closing this, since the samba and other Linux plugins are no longer a priority.