Bug 49771 - Usability for new share creation
Usability for new share creation
Status: NEW
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
https://help.univention.com/t/problem...
:
: 50419 (view as bug list)
Depends on: 44054
Blocks:
  Show dependency treegraph
 
Reported: 2019-07-01 16:18 CEST by Christina Scheinig
Modified: 2019-10-29 20:28 CET (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 4: Will affect most installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.091
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019062521000734
Bug group (optional): Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christina Scheinig univentionstaff 2019-07-01 16:18:05 CEST
With bug 44054 we optimized the blacklist handling for share paths.
This causes the usability for the user to decrease enormously.

Not knowing the blacklist path behaviour a customer creates a share beneath /var/share


The share is now created in ldap, but not created in samba. So the share is not visible via windows.

The message in the listener.log is a good hint, so now the recommended ucr variables can be set. That you have to restart listener is mentioned in the ucr variable. But doing this there still no share in windows visible.

So you have to modify the share or rerun the listener module to make the share created completely.

Setting a new path for the share is not enough to create the share.

--------------------------------------------------------------------------
To make this handling more easy for the user we could consider, to show a hint in the UMC when the share is to be created in a blacklisted path.

If the path is whitelisted, we may trigger the share creation in some way, or describe exactly the necessary steps.
Comment 1 Arvid Requate univentionstaff 2019-10-29 20:24:32 CET
*** Bug 50419 has been marked as a duplicate of this bug. ***
Comment 2 Arvid Requate univentionstaff 2019-10-29 20:28:50 CET
This may be two Bugs:

1. Maybe the directory should not be created when it is blacklisted anyway.

2. There is no feedback to the user in UMC.


The first could be easy to fix. The second is a valid concern but may require some conceptual changes.
I just closed Bug 50419 as a duplicate of this, but maybe we should fix the first point via that bug and handle the feedback issue on this one?