Bug 41708 - post-enabling optional "samba": Object class violation 'univentionShareSamba' requires attribute 'univentionShareSambaName'
post-enabling optional "samba": Object class violation 'univentionShareSamba'...
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Shares
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-06-29 21:25 CEST by Philipp Hahn
Modified: 2019-01-03 07:18 CET (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 2: Will only affect a few 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.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2016-06-29 21:25:14 CEST
1. Create a NFS-only share
2. Modify share entry and enable option "samba"
3. Save entry

Das LDAP-Objekt konnte nicht gespeichert werden:
 LDAP-Fehler Object class violation:
  object class 'univentionShareSamba' requires attribute 'univentionShareSambaName'
Comment 1 Jannik Ahlers univentionstaff 2018-01-11 10:26:45 CET
The bug occurs only when editing the share, and when removing the value of the attribute univentionShareSambaName. It has nothing to do with enabling/disabling samba.
If you leave the samba name field empty during the creation of a share object, the value gets autofilled with the share's name. This does not happen when editing the object.
As the samba name is needed even when samba is disabled, the attribute should be set to required.

see branch jahlers/41708-post-enable-samba
Comment 2 Florian Best univentionstaff 2018-01-11 17:04:00 CET
Very good!
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:18:09 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.