Univention Bugzilla – Bug 41785
modrdn() always performed when attribute name contains uppercase characters
Last modified: 2016-10-04 13:13:51 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.
univention-python (9.0.1-8): r70958 | Bug #41785: don't do modrdn() for equal DN's univention-python.yaml: r70959 | YAML Bug #41785
Ticket#2016071121000746
Ticket#2016071321000402
Jenkins tests: OK, working again YAML: OK Code review: OK Manual tests: OK
<http://errata.software-univention.de/ucs/4.1/211.html>
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];