Bug 41785 - modrdn() always performed when attribute name contains uppercase characters
modrdn() always performed when attribute name contains uppercase characters
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: univention-lib
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1-2-errata
Assigned To: Florian Best
Stefan Gohmann
:
Depends on:
Blocks: 41867
  Show dependency treegraph
 
Reported: 2016-07-13 10:10 CEST by Florian Best
Modified: 2016-10-04 13:13 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 4: Will affect most installed domains
How will those affected feel about the bug?: 4: A User would return the product
User Pain: 0.457
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2016071121000746,2016071321000402
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 Florian Best univentionstaff 2016-07-13 10:10:45 CEST
When modifying a UDM object which has uppercase characters in its identifying DN attribute name there is always a modrdn operation done with the same DN as before.

# strace python -c "__import__('univention.uldap').uldap.getMachineConnection(0).modify('univentionAppID=samba4_4.3,cn=samba4,cn=apps,cn=univention,dc=school,dc=local', [])" 2>&1 | grep univentionAppID                                                             
write(3, "0s\2\1\2ln\4MuniventionAppID=samba4_"..., 117) = 117

Regression due to svn r70685 / Bug #40041 / UCS 4.1-2 errata 207.
Comment 1 Florian Best univentionstaff 2016-07-13 10:35:50 CEST
univention-python (9.0.1-8):
r70958 | Bug #41785: don't do modrdn() for equal DN's

univention-python.yaml:
r70959 | YAML Bug #41785
Comment 2 Jens Thorp-Hansen univentionstaff 2016-07-13 15:51:16 CEST
Ticket#2016071121000746
Comment 3 Jens Thorp-Hansen univentionstaff 2016-07-13 16:36:44 CEST
Ticket#2016071321000402
Comment 4 Stefan Gohmann univentionstaff 2016-07-14 06:30:54 CEST
Jenkins tests: OK, working again

YAML: OK

Code review: OK

Manual tests: OK
Comment 5 Janek Walkenhorst univentionstaff 2016-07-14 11:33:52 CEST
<http://errata.software-univention.de/ucs/4.1/211.html>
Comment 6 Philipp Hahn univentionstaff 2016-07-18 10:36:22 CEST
Ticket#2016071421000581:

DC used problemativ version,
error persists in transaction log,
slave ill fails to replicate problematic transactions:

>14.07.16 10:45:04.996  move_same_dn(zoneName=XXX.de,cn=dns,dc=XXX,dc=de)
>14.07.16 10:45:04.996  replication: rename phase I: zoneName=XXX.de,cn=dns,dc=XXX,dc=de (entryUUID=adf352e8-3752-1035-85d1-c7258dda5036)
>14.07.16 10:45:05.003  replication: rename phase II: zoneName=XXX.de,cn=dns,dc=XXX,dc=de (entryUUID=adf352e8-3752-1035-85d1-c7258dda5036)
>14.07.16 10:45:05.003  replication: the rename target already exists in the local LDAP, backup and remove the dn: zoneName=XXX.de,cn=dns,dc=XXX,dc=de
>14.07.16 10:45:05.004  replication: dump zoneName=XXX.de,cn=dns,dc=XXX,dc=de to /var/univention-backup/replication/1468485905.0
>14.07.16 10:45:05.014  Failed to delete non leaf object: dn=[zoneName=XXX.de,cn=dns,dc=XXX,dc=de];